| 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
| ||
|
Message-ID: <20070924180041.GB2435@infradead.org> Date: Mon, 24 Sep 2007 19:00:41 +0100 From: Christoph Hellwig <hch@...radead.org> To: Randy Dunlap <randy.dunlap@...cle.com> Cc: Christoph Hellwig <hch@...radead.org>, Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, "Frank Ch. Eigler" <fche@...hat.com> Subject: Re: [patch 6/7] Linux Kernel Markers - Documentation On Mon, Sep 24, 2007 at 10:56:32AM -0700, Randy Dunlap wrote: > I don't have a problem with a samples/ directory except (as I have > already pointed out) it means that people will end up having to look > in 2 places for the information that they need, i.e., both in > samples/ and in Documentation/. So I really don't see a big need > to split the samples and docs. > > What's wrong with building sample code in the Documentation/ directory? It's not really documentation, it's code :) If you want to build documentation from the samples use kerneldoc or similar to extrace the comments. Having Documentation/ purely for things not affecting the build make things a whole lot clearer, but if you absolutely insist on it we can put it under Documentation/ as long as it's fully integrated into kbuild and will be built as part of allmodconfig, unlike the current two patches showing code there. - 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/
Powered by blists - more mailing lists