linux-kernel - Re: [patch 6/7] Linux Kernel Markers

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: <20070924123842.64cf298b.randy.dunlap@oracle.com>
Date:	Mon, 24 Sep 2007 12:38:42 -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>,
	Prasanna S Panchamukhi <prasanna@...ibm.com>,
	Jim Keniston <jkenisto@...ibm.com>
Subject: Re: [patch 6/7] Linux Kernel Markers - Documentation

On Mon, 24 Sep 2007 20:25:04 +0100 Christoph Hellwig wrote:

> On Mon, Sep 24, 2007 at 03:18:11PM -0400, Mathieu Desnoyers wrote:
> > > 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.
> > > 
> > 
> > One should have a look at Documentation/kprobes.txt for that kind of
> > example code / documentation mix.
> 
> That one is particularly bad.  It's high on my todo list of things to fix.
> -

I already have it split and building.   Just need to know
where to put it.  :)


---
~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/