[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070919174845.GD3115@uranus.ravnborg.org>
Date: Wed, 19 Sep 2007 19:48:45 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Christoph Hellwig <hch@...radead.org>,
Randy Dunlap <randy.dunlap@...cle.com>,
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, Sep 19, 2007 at 05:55:07PM +0100, Christoph Hellwig wrote:
> On Wed, Sep 19, 2007 at 09:52:23AM -0700, Randy Dunlap wrote:
> > That's why they exmaples should not be hidden/embedded in .txt files;
> > they should be standalone .c files with makefiles etc.
>
> Yes. And most importantly integrated with the kernel build system.
>
> > and they can be taken out of Documentation/ whenever they go into
> > util-linux-ng or elsewhere. Let's get the order correct.
>
> Well, this is kernel code - so util-linux is not the solution here
> obviously :)
Can you sketch what you have in mind.
We right now have said we wnated to:
1) include a framework for executing simple new-syscall-test-stubs
2) have a nice place for kernel example code
I could come up with something but I expect you already have something
in your mind where to put stuff.
If I have a rough idea I can start looking into the kbuild bits of it.
Not that I will have it ready within the next two weeks but nice buffer
when I anyway drop sleeping..
Sam
-
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