linux-kernel - Re: API documentation (was [PATCH] Replace completions with semaphores)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e2e108260804141138s4d8badbrf389134f6923ad46@mail.gmail.com>
Date:	Mon, 14 Apr 2008 20:38:32 +0200
From:	"Bart Van Assche" <bart.vanassche@...il.com>
To:	"Peter Zijlstra" <peterz@...radead.org>
Cc:	"Jonathan Corbet" <corbet@....net>,
	"Matthew Wilcox" <matthew@....cx>,
	"Roland Dreier" <rdreier@...co.com>,
	"Ingo Oeser" <ioe-lkml@...eria.de>,
	"Daniel Walker" <dwalker@...sta.com>, linux-kernel@...r.kernel.org,
	"Linus Torvalds" <torvalds@...l.org>, "Ingo Molnar" <mingo@...e.hu>
Subject: Re: API documentation (was [PATCH] Replace completions with semaphores)

On Mon, Apr 14, 2008 at 7:33 PM, Peter Zijlstra <peterz@...radead.org> wrote:
>  Books should only be used to obtain the general picture, any details
>  will be instantly-obsolete, esp at the pace Linux changes.
>
>  Most of the concepts from LDD3 are still valid, many of the details are
>  dead wrong.
>
>  Can't we make LDD4 a high level book, explcitly mentioning how people
>  should go about obtaining details? Like go ask on #kernelnewbies and the
>  sorts.
>
>  The thing I always tell #kernelnewbies people is to look at a related
>  driver (of course that kite doesn't always fly). Another good way to
>  learn stuff is to just read the implementation.
>
>  A 'trick' that is often useful is to look in git to see how something
>  was changed, provided you knew how to do it some time in the past.

What I remember from the first time I wrote a network driver is that
reading the chapter in LDD3 about network drivers was the fastest way
to get started. Learning how to write a network driver by reverse
engineering existing drivers would have required much more time. My
opinion is that mentioning all relevant details in a book makes sense.

Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/