linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Shuah Khan <shuah@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Francis Deslauriers <francis.deslauriers@efficios.com>,
	peterz@infradead.org, mathieu.desnoyers@efficios.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] selftests/ftrace: Fix kprobe string testcase to not probe notrace function
Date: Fri, 27 Jul 2018 21:47:13 +0900	[thread overview]
Message-ID: <20180727214713.a6e5743c5aa5cb12413af72e@kernel.org> (raw)
In-Reply-To: <555469b9-a866-60f1-6856-e8bd80f99591@kernel.org>

On Thu, 26 Jul 2018 15:22:22 -0600
Shuah Khan <shuah@kernel.org> wrote:

> On 07/26/2018 01:58 PM, Steven Rostedt wrote:
> > On Thu, 26 Jul 2018 16:44:09 +0900
> > Masami Hiramatsu <mhiramat@kernel.org> wrote:
> > 
> >> On Thu, 26 Jul 2018 14:54:23 +0900
> >> Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >>
> >>> Fix kprobe string argument testcase to not probe notrace
> >>> function. Instead, it probes tracefs function which must
> >>> be available with ftrace.  
> >>
> >> Oops, this must be sent to Shuah too.
> >>
> >> Shuah, I think you can freely pick this patch to kselftest
> >> branch, since this removes a dependency of notrace functions,
> >> not depends on any new feature :)
> >>
> > 
> > Shuah,
> > 
> > Please take this patch in your tree. I'll take the other two.
> > 
> > Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> > 
> > -- Steve
> > 
> 
> Steve,
> 
> yes. I will pick this up.

Thanks Steve and Shuah!

> 
> thanks,
> -- Shuah
> 
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2018-07-27 12:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26  5:52 [PATCH v2 0/3] tracing: kprobes: Prohibit probing on notrace functions Masami Hiramatsu
2018-07-26  5:53 ` [PATCH v2 1/3] tracing: kprobes: Prohibit probing on notrace function Masami Hiramatsu
2018-07-28  1:00   ` Masami Hiramatsu
2018-07-28  8:11   ` kbuild test robot
2018-07-28 13:42     ` Masami Hiramatsu
2018-07-28  8:24   ` kbuild test robot
2018-07-26  5:53 ` [PATCH v2 2/3] selftest/ftrace: Move kprobe selftest function to separate compile unit Masami Hiramatsu
2018-07-26 23:29   ` Steven Rostedt
2018-07-27 12:39     ` Masami Hiramatsu
2018-07-27 12:44     ` [PATCH v2.1 " Masami Hiramatsu
2018-07-26  5:54 ` [PATCH v2 3/3] selftests/ftrace: Fix kprobe string testcase to not probe notrace function Masami Hiramatsu
2018-07-26  7:44   ` Masami Hiramatsu
2018-07-26 19:58     ` Steven Rostedt
2018-07-26 21:22       ` Shuah Khan
2018-07-27 12:47         ` Masami Hiramatsu [this message]
2018-07-27 14:26           ` Shuah Khan
2018-07-27 14:31             ` Steven Rostedt
2018-07-28  2:24               ` Masami Hiramatsu
2018-07-27 21:43   ` Steven Rostedt
2018-07-27 23:59     ` Masami Hiramatsu

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=20180727214713.a6e5743c5aa5cb12413af72e@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=francis.deslauriers@efficios.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.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).