| 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
| ||
|
Date: Mon, 24 Sep 2007 10:56:32 -0700 From: Randy Dunlap <randy.dunlap@...cle.com> To: Christoph Hellwig <hch@...radead.org> Cc: 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, 24 Sep 2007 18:50:44 +0100 Christoph Hellwig wrote: > On Mon, Sep 24, 2007 at 12:49:56PM -0400, Mathieu Desnoyers wrote: > > Here is some documentation explaining what is/how to use the Linux > > Kernel Markers. > > As mentioned in the tracing infrastructure thread I don't think > putting code into Documentation is a good idea. Either of you really > should start a sample/ toplevel directory for this kind of stuff > including a Kconfig menu etc to be able to build these samples as > part of an allmodconfig. 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? --- ~Randy Phaedrus says that Quality is about caring. - 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