From: Shuah Khan <shuah@kernel.org>
To: Shuah Khan <shuahkh@osg.samsung.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: Thomas Meyer <thomas@m3y3r.de>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 1/3] selftests/ftrace: multiple_kprobes: Also check for support
Date: Tue, 19 Sep 2017 08:47:31 -0600 [thread overview]
Message-ID: <1bd826c2-be22-fed0-e7ee-5584d1ceab70@kernel.org> (raw)
In-Reply-To: <39e2f1e9-5d41-bf7d-42a6-61986099b750@osg.samsung.com>
On 09/18/2017 09:19 AM, Shuah Khan wrote:
> On 09/18/2017 09:18 AM, Steven Rostedt wrote:
>> On Thu, 14 Sep 2017 08:15:19 -0700
>> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>>
>>
>>>> Hi Steve/Masami,
>>>>
>>>> This patch looks good to me. Adds a check similar to the one one in
>>>> tools/testing/selftests/ftrace/test.d/kprobe/functions
>>>
>>> Yes, this looks good to me too :)
>>>
>>> Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
>>>
>>
>> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
>>
>> -- Steve
>>
>
> Thanks Steve and Masami,
>
> I will get this into rc2
>
Applied to linux-kselftest fixes 4.14-rc2
thanks,
-- Shuah
prev parent reply other threads:[~2017-09-19 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 12:01 [PATCH 1/3] selftests/ftrace: multiple_kprobes: Also check for support Thomas Meyer
2017-09-08 12:01 ` [PATCH 2/3] selftests/intel_pstate: No need to compile test progs in the run script Thomas Meyer
2017-09-14 14:59 ` Shuah Khan
2017-09-08 12:01 ` [PATCH 3/3] selftests/net: msg_zerocopy enable build with older kernel headers Thomas Meyer
2017-09-14 14:58 ` [PATCH 1/3] selftests/ftrace: multiple_kprobes: Also check for support Shuah Khan
2017-09-14 15:15 ` Masami Hiramatsu
2017-09-15 19:10 ` Steven Rostedt
2017-09-18 15:18 ` Steven Rostedt
2017-09-18 15:19 ` Shuah Khan
2017-09-19 14:47 ` Shuah Khan [this message]
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=1bd826c2-be22-fed0-e7ee-5584d1ceab70@kernel.org \
--to=shuah@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuahkh@osg.samsung.com \
--cc=thomas@m3y3r.de \
/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