From: Randy Dunlap <randy.dunlap@oracle.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: "David J. Wilder" <dwilder@us.ibm.com>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
ananth@in.ibm.com
Subject: Re: [RFC Patch] Trace - Samples
Date: Tue, 25 Sep 2007 16:30:55 -0700 [thread overview]
Message-ID: <46F99A2F.7000607@oracle.com> (raw)
In-Reply-To: <20070925232735.GA22967@Krystal>
Mathieu Desnoyers wrote:
> * Randy Dunlap (randy.dunlap@oracle.com) wrote:
>> On Tue, 25 Sep 2007 13:35:47 -0700 David J. Wilder wrote:
>>
>>> This patch Moves the trace example into the new samples/ infrastructure
>>>
>>> Requires: [patch 3/5] Add samples subdir (http://lkml.org/lkml/2007/9/25/157)
>>> and create samples/Makefile or apply:
>>> [patch 4/5] Linux Kernel Markers - Samples (http://lkml.org/lkml/2007/9/25/166)
>>>
>>> Signed-off-by: David Wilder <dwilder@us.ibm.com>
>> Looks good. Thanks.
>>
>> Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
>>
>> Andrew, Mathieu is making changes to patch 3/5 referenced above.
>> When that is done, do you need a resend of all of these samples/
>> patches or do you have them straight?
>>
>> Basically we have:
>> a. add samples/ infrastructure (new coming from Mathieu)
>> b. add markers to samples/ (Mathieu)
> Mine is correct as is. (with the new samples infrastructure)
>
Right, your 2 can be the base (basis) for samples/, then the other
follow-ups can be applied.
>
>> c. add trace/ to samples/ (this patch from David)
>> d. add kprobes/ to samples (move some from Documentation)
--
~Randy
Phaedrus says that Quality is about caring.
next prev parent reply other threads:[~2007-09-25 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 20:35 [RFC Patch] Trace - Samples David J. Wilder
2007-09-25 21:16 ` Randy Dunlap
2007-09-25 23:27 ` Mathieu Desnoyers
2007-09-25 23:30 ` Randy Dunlap [this message]
2007-09-26 15:14 ` 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=46F99A2F.7000607@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=ananth@in.ibm.com \
--cc=dwilder@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.