linux-kernel - Re: [Patch 1/2] Trace code and documentation (updated)

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: <20070919095223.83bd8226.randy.dunlap@oracle.com>
Date:	Wed, 19 Sep 2007 09:52:23 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	David Wilder <dwilder@...ibm.com>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: [Patch 1/2] Trace code and documentation (updated)

On Wed, 19 Sep 2007 17:20:18 +0100 Christoph Hellwig wrote:

> On Wed, Sep 19, 2007 at 07:14:47AM -0700, David Wilder wrote:
> > I agree with you; however, this is in the example code in the 
> > Documentation directory,  It is not part of the trace code.  The example 
> > was just meant to be a demonstration of how the interface works.
> 
> So we tell people to write bad code?  Wonderful..
> 
> And while we're at it can we please stop the dumb idea to put example
> code into Documentation?  If example code doesn't get build during a
> make oldconfig it will bitrot real fast and not be useful at all.


That's why they exmaples should not be hidden/embedded in .txt files;
they should be standalone .c files with makefiles etc.

I've built and corrected several of them, but they would be more
likely to be kept up-to-date if they are more available in standalone
files.

and they can be taken out of Documentation/ whenever they go into
util-linux-ng or elsewhere.  Let's get the order correct.

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