lkml.org 
[lkml]   [1997]   [Jul]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: documenting the kernel [and some praise :-)]
Date
> in mind one danger with the approach suggested above: What happens if some
> kind soul contributes documentation for a certain piece of the code, then a
> developer comes along and changes the code? The documentation will no
> longer match the code and in fact might become completely wrong. And *wrong*
> documentation would IMHO be even worse than no documentation. So there
> would have to be some way to insure that the documentation would either be
> updated or remove when the code gets changed.

The documentation needs a correct as of version XYZ and the code possibly
a version tag - that would be very good practice anyway.

Ok can folks on the list do me a favour - can everyone with a working/nonworking
network card in 2.0.31p2 (or p2 and Dr Werners patches) mail

card-summary@lxorguk.ukuu.org.uk a one liner in the format

manufacturer : card : version(if exists) : works Y/N : interface (10/100) T/2..

with comments below on why it doesnt work, or what it does odd

For the 3c59x/3c90x drivers and the tulip drivers. If its a tulip also
state if using the DEC DE4x5 driver works instead. If you happen to know
some other version works let me know that too. Im going to try and produce
a compatibility matrix for them

Alan


\
 
 \ /
  Last update: 2005-03-22 13:39    [W:2.267 / U:0.340 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site