| 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: <20070510114158.GA16741@infradead.org> Date: Thu, 10 May 2007 12:41:58 +0100 From: Christoph Hellwig <hch@...radead.org> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: Christoph Hellwig <hch@...radead.org>, Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [patch 07/10] Linux Kernel Markers - Documentation On Thu, May 10, 2007 at 12:41:20PM +0100, Alan Cox wrote: > On Thu, 10 May 2007 07:58:47 +0100 > Christoph Hellwig <hch@...radead.org> wrote: > > > On Wed, May 09, 2007 at 09:56:02PM -0400, Mathieu Desnoyers wrote: > > > Here is some documentation explaining what is/how to use the Linux > > > Kernel Markers. > > > > Please remove all references to out of tree code from the kernel documentation. > > Christoph stop being ridiculous. Its one thing to object to kernel > markers I do not object kernel markers, and I have no idea where you got that crap from. Quite contrary I've worked with Matthew on getting both markers and lttng good enough that we can merge it eventually. Documentation of kernel facilities should not mention big outside blobs of crap nerverless, which is something totally different from not mentionining userspace code contrary to your ill-advised position. - 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