public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Wilder <dwilder@us.ibm.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [Patch 1/2] Trace code and documentation (resend)
Date: Mon, 24 Sep 2007 09:13:10 -0700	[thread overview]
Message-ID: <20070924091310.c306df35.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070924154114.GA25368@infradead.org>

On Mon, 24 Sep 2007 16:41:14 +0100 Christoph Hellwig wrote:

> On Mon, Sep 24, 2007 at 08:38:34AM -0700, David Wilder wrote:
> > >NACK, don't put code into Documentation/.  Put it into kernel as it's
> > >actually useful kernel code.  
> > 
> > Are you suggesting moving the example code into kernel? Or complaining 
> > about example code in /Documentation?
> 
> Both.  example code should be integrated with the build system so it
> gets built.

How about if we build the sample files in the Documentation/ tree?

with added Kconfig, Makefiles etc.


> > And add clone,exec and exit while you're at it.
> > 
> > Hu?  A syscall tracer sounds like a nice idea but that is not what I am 
> > trying to accomplish.  I will let Systemtap handle that.
> 
> Systemtap doesn't help anyone as it's not in the tree.  I haven't even
> asked you to provide a full system call tracing modulem but provide at
> least one that's useful for a certain use-case (looking at processes)
> instead of almost useless code.

---
~Randy
Phaedrus says that Quality is about caring.

  reply	other threads:[~2007-09-24 16:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22  4:23 [Patch 1/2] Trace code and documentation (resend) David J. Wilder
2007-09-22  9:35 ` Christoph Hellwig
2007-09-24 15:38   ` David Wilder
2007-09-24 15:41     ` Christoph Hellwig
2007-09-24 16:13       ` Randy Dunlap [this message]
2007-09-24 16:32       ` 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=20070924091310.c306df35.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=dwilder@us.ibm.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.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