[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070919175109.GA23889@infradead.org>
Date: Wed, 19 Sep 2007 18:51:09 +0100
From: Christoph Hellwig <hch@...radead.org>
To: Sam Ravnborg <sam@...nborg.org>
Cc: 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 07:48:45PM +0200, Sam Ravnborg wrote:
> > 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..
I think for samples we just want a samples/ toplevel directory with
normal Kbuild and Kconfig files. Not any different from drivers or
filesystems, just a new hiearchary.
tests stuff was rather disliked by Linus, so I wonder wether we should
go ahead with it. We'd need a test driver like expect to driver the
testcases.
-
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