From: David Wilder <dwilder@us.ibm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org,
SystemTAP <systemtap@sources.redhat.com>,
akpm@linux-foundation.org
Subject: Re: [PATCH 1/2] Trace code and documentation
Date: Fri, 14 Sep 2007 21:49:31 -0700 [thread overview]
Message-ID: <46EB645B.6000302@us.ibm.com> (raw)
In-Reply-To: <20070914175027.GA3642@uranus.ravnborg.org>
Sam Ravnborg wrote:
> Hi David.
>
> A random comment to the code.
> Several of the struct file_operations are not declared static as
> they should be.
>
> Btw. it looks good from a coding style point-of-view.
>
> About the name what about ktrace??
>
> Sam
>
>
Thanks for the comment. I sure don't want to change the name a forth
time, can we live with "trace"?
next prev parent reply other threads:[~2007-09-15 4:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 23:43 [PATCH 1/2] Trace code and documentation David Wilder
2007-09-14 4:12 ` Randy Dunlap
2007-09-14 17:50 ` Sam Ravnborg
2007-09-15 4:49 ` David Wilder [this message]
2007-09-15 5:18 ` Sam Ravnborg
2007-09-15 1:08 ` Andrew Morton
2007-09-15 1:40 ` Randy Dunlap
2007-09-15 4:47 ` David Wilder
2007-09-15 16:01 ` 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=46EB645B.6000302@us.ibm.com \
--to=dwilder@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=systemtap@sources.redhat.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