From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [ftrace/kprobes PATCH 0/3] tracing: probeevent: Fix module symbol probing
Date: Wed, 3 Oct 2018 22:26:17 +0900 [thread overview]
Message-ID: <20181003222617.b4906d8b7156ebf6aec2c1c1@kernel.org> (raw)
In-Reply-To: <20181002224714.009682f0@vmware.local.home>
On Tue, 2 Oct 2018 22:47:14 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 1 Oct 2018 11:48:55 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Thu, 27 Sep 2018 19:48:58 +0900
> > Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >
> > > Hello Steve,
> > >
> > > Could you also include this series to the branch?
> > >
> >
> > Hi Masami,
> >
> > I just came back from Embedded / Kernel Recipes, I'll look at these
> > today.
> >
>
> Unfortunately, I've been pulled off to other tasks :-(
>
> I'll make it a priority tomorrow (Wednesday).
No problem, thank you for reviewing :)
>
> -- Steve
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2018-10-03 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 16:17 [ftrace/kprobes PATCH 0/3] tracing: probeevent: Fix module symbol probing Masami Hiramatsu
2018-08-28 16:17 ` [ftrace/kprobes PATCH 1/3] tracing/uprobes: Fix to return -EFAULT if copy_from_user failed Masami Hiramatsu
2018-08-28 16:18 ` [ftrace/kprobes PATCH 2/3] tracing/kprobes: Check the probe on unloaded module correctly Masami Hiramatsu
2018-08-28 16:18 ` [ftrace/kprobes PATCH 3/3] tracing/kprobes: Allow kprobe-events to record module symbol Masami Hiramatsu
2018-10-03 19:12 ` Steven Rostedt
2018-10-04 1:11 ` Steven Rostedt
2018-10-05 8:53 ` Masami Hiramatsu
2018-09-27 10:48 ` [ftrace/kprobes PATCH 0/3] tracing: probeevent: Fix module symbol probing Masami Hiramatsu
2018-10-01 15:48 ` Steven Rostedt
2018-10-03 2:47 ` Steven Rostedt
2018-10-03 13:26 ` Masami Hiramatsu [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=20181003222617.b4906d8b7156ebf6aec2c1c1@kernel.org \
--to=mhiramat@kernel.org \
--cc=dan.carpenter@oracle.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).