From: Christoph Hellwig <hch@infradead.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Christoph Hellwig <hch@infradead.org>,
David Wilder <dwilder@us.ibm.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Test harness in the kernel for new syscalls? [Was: Trace code and documentation (updated)]
Date: Fri, 21 Sep 2007 09:08:08 +0100 [thread overview]
Message-ID: <20070921080808.GB29050@infradead.org> (raw)
In-Reply-To: <20070920215042.38fd3546.randy.dunlap@oracle.com>
On Thu, Sep 20, 2007 at 09:50:42PM -0700, Randy Dunlap wrote:
> so kernel sample code goes in the new samples/ directory,
> and userspace sample code gets pushed to util-linux ?
I'm not sure we want to have purely sample code in util-linux, but rather
extended sample code that makes some use. So if you're writing user space
sample code for your new feature make sure it's somewhat production quality,
has a useful interface and write a little manpage for it. That'll also help
us to win sysdamins hearts back because BSD and solaris already have all these
neat little tools that need to be hacked from scratch in perl on Linux.
For kernel code a samples dir might make sense because say a demo of the
firmware loader (one of those things in Documentation/ right now) of
course never can be "real" code. OTOH a fork probe as provided with the
tracing code sounds more like a real thing that should go into drivers/misc/.
next prev parent reply other threads:[~2007-09-21 8:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 4:46 [Patch 1/2] Trace code and documentation (updated) David J. Wilder
2007-09-19 8:30 ` Andi Kleen
2007-09-19 14:14 ` David Wilder
2007-09-19 15:38 ` Andi Kleen
2007-09-19 16:20 ` Christoph Hellwig
2007-09-19 16:52 ` Randy Dunlap
2007-09-19 16:55 ` Christoph Hellwig
2007-09-19 17:48 ` Sam Ravnborg
2007-09-19 17:51 ` Christoph Hellwig
2007-09-19 18:01 ` Test harness in the kernel for new syscalls? [Was: Trace code and documentation (updated)] Sam Ravnborg
2007-09-21 4:50 ` Randy Dunlap
2007-09-21 6:33 ` Randy Dunlap
2007-09-21 8:08 ` Christoph Hellwig [this message]
2007-09-19 17:41 ` [Patch 1/2] Trace code and documentation (updated) David Wilder
2007-09-23 12:46 ` Christoph Hellwig
2007-09-24 15:16 ` David Wilder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070921080808.GB29050@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=dwilder@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®