From: Christoph Hellwig <hch@infradead.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
"Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: [patch 6/7] Linux Kernel Markers - Documentation
Date: Mon, 24 Sep 2007 19:30:42 +0100 [thread overview]
Message-ID: <20070924183042.GA4418@infradead.org> (raw)
In-Reply-To: <46F800A7.7090005@oracle.com>
On Mon, Sep 24, 2007 at 11:23:35AM -0700, Randy Dunlap wrote:
> That might be OK for this case, but sometimes it makes sense to have
> README etc. about how to use the software. So you would want this
> in the Documentation/ tree? That makes it harder on users.
If it's so complex that we can't describe it in a few dozens lines
it shouldn't be anywhere but the place it belongs and better have a
real use and not just be a sample. And in the trace case I must
admit that I'd prefer a real use like some simple syscall-trace
over this hack anyway..
next prev parent reply other threads:[~2007-09-24 18:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 16:49 [patch 0/7] Linux Kernel Markers (redux) Mathieu Desnoyers
2007-09-24 16:49 ` [patch 1/7] Seq_file add support for sorted list Mathieu Desnoyers
2007-09-24 17:37 ` Christoph Hellwig
2007-09-24 17:52 ` Mathieu Desnoyers
2007-09-24 17:55 ` Christoph Hellwig
2007-09-24 16:49 ` [patch 2/7] Sort module list by pointer address to get coherent sleepable seq_file iterators Mathieu Desnoyers
2007-09-24 16:49 ` [patch 3/7] Combine instrumentation menus in kernel/Kconfig.instrumentation Mathieu Desnoyers
2007-09-24 16:49 ` [patch 4/7] Linux Kernel Markers - Architecture Independent Code Mathieu Desnoyers
2007-09-24 17:48 ` Christoph Hellwig
2007-09-24 18:15 ` Robert P. J. Day
2007-09-24 18:19 ` Christoph Hellwig
2007-09-24 18:22 ` Mathieu Desnoyers
2007-09-24 18:43 ` Mathieu Desnoyers
2007-09-24 18:45 ` Christoph Hellwig
2007-09-24 18:53 ` Mathieu Desnoyers
2007-09-24 16:49 ` [patch 5/7] Linux Kernel Markers - Use instrumentation kconfig menu Mathieu Desnoyers
2007-09-24 17:49 ` Christoph Hellwig
2007-09-24 18:45 ` Mathieu Desnoyers
2007-09-24 16:49 ` [patch 6/7] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-09-24 17:50 ` Christoph Hellwig
2007-09-24 17:56 ` Randy Dunlap
2007-09-24 18:00 ` Christoph Hellwig
2007-09-24 18:13 ` Randy Dunlap
2007-09-24 18:19 ` Christoph Hellwig
2007-09-24 18:23 ` Randy Dunlap
2007-09-24 18:30 ` Christoph Hellwig [this message]
2007-09-24 18:49 ` Randy Dunlap
2007-09-24 18:54 ` Christoph Hellwig
2007-09-24 18:56 ` Randy Dunlap
2007-09-24 20:37 ` Randy Dunlap
2007-09-24 21:08 ` Mathieu Desnoyers
2007-09-24 21:12 ` Randy Dunlap
2007-09-25 4:10 ` Mathieu Desnoyers
2007-09-25 5:31 ` Randy Dunlap
2007-09-25 11:00 ` Mathieu Desnoyers
2007-09-24 19:18 ` Mathieu Desnoyers
2007-09-24 19:25 ` Christoph Hellwig
2007-09-24 19:38 ` Randy Dunlap
2007-09-25 1:31 ` Steven Rostedt
2007-09-25 8:21 ` Christoph Hellwig
2007-09-24 16:49 ` [patch 7/7] Port of blktrace to the Linux Kernel Markers Mathieu Desnoyers
2007-09-24 18:11 ` [patch 0/7] Linux Kernel Markers (redux) Christoph Hellwig
2007-09-24 19:04 ` Mathieu Desnoyers
2007-09-24 19:07 ` Christoph Hellwig
2007-09-24 19:24 ` Mathieu Desnoyers
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=20070924183042.GA4418@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=randy.dunlap@oracle.com \
/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