From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH 1/2] ftracetest: add kprobes on ftrace testcase
Date: Tue, 21 Oct 2014 21:10:00 +0900 [thread overview]
Message-ID: <54464D18.5070807@hitachi.com> (raw)
In-Reply-To: <20141021115928.GB4161@osiris>
(2014/10/21 20:59), Heiko Carstens wrote:
> On Tue, Oct 21, 2014 at 06:21:05PM +0900, Masami Hiramatsu wrote:
>> (2014/10/20 19:52), Heiko Carstens wrote:
>>> Add a kprobes on ftrace testcase. The testcase verifies that
>>> - enabling and disabling function tracing works on a function which
>>> already contains a dynamic kprobe
>>> - adding and removing a dynamic kprobe works on a function which is
>>> already enabled for function tracing
>>>
>>
>> Looks good to me.
>>
>>> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
>>
>> Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
>
> Hi Masami,
>
> thanks! How should these two patches go upstream?
Steven, could you pick this series to your tree?
I think it is better to manage ftracetest testcases in one tree.
Thank you,
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2014-10-21 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 10:52 [PATCH 0/2] ftracetest improvement and new testcase Heiko Carstens
2014-10-20 10:52 ` [PATCH 1/2] ftracetest: add kprobes on ftrace testcase Heiko Carstens
2014-10-21 9:21 ` Masami Hiramatsu
2014-10-21 11:59 ` Heiko Carstens
2014-10-21 12:10 ` Masami Hiramatsu [this message]
2014-10-22 15:04 ` Steven Rostedt
2014-10-23 1:04 ` Masami Hiramatsu
2014-10-20 10:52 ` [PATCH 2/2] ftracetest: sort testcases Heiko Carstens
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=54464D18.5070807@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).