From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andreas Ziegler <andreas.ziegler@fau.de>,
Ingo Molnar <mingo@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: uprobes: fix typo in pr_fmt string
Date: Fri, 18 Jan 2019 08:28:37 +0900 [thread overview]
Message-ID: <20190118082837.6a4ff0668bf2d9e80846e454@kernel.org> (raw)
In-Reply-To: <20190117095316.303dafc2@vmware.local.home>
On Thu, 17 Jan 2019 09:53:16 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> Masami,
>
> Can you give an Acked-by?
Of course!
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thank you Andreas!
>
> Thanks!
>
> -- Steve
>
>
> On Thu, 17 Jan 2019 14:30:23 +0100
> Andreas Ziegler <andreas.ziegler@fau.de> wrote:
>
> > The subsystem-specific message prefix for uprobes was also
> > "trace_kprobe: " instead of "trace_uprobe: " as described in
> > the original commit message.
> >
> > Fixes: 7257634135c24 ("tracing/probe: Show subsystem name in messages")
> > Signed-off-by: Andreas Ziegler <andreas.ziegler@fau.de>
> > ---
> > kernel/trace/trace_uprobe.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
> > index e335576b9411..19a1a8e19062 100644
> > --- a/kernel/trace/trace_uprobe.c
> > +++ b/kernel/trace/trace_uprobe.c
> > @@ -5,7 +5,7 @@
> > * Copyright (C) IBM Corporation, 2010-2012
> > * Author: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> > */
> > -#define pr_fmt(fmt) "trace_kprobe: " fmt
> > +#define pr_fmt(fmt) "trace_uprobe: " fmt
> >
> > #include <linux/ctype.h>
> > #include <linux/module.h>
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2019-01-17 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 13:30 [PATCH] tracing: uprobes: fix typo in pr_fmt string Andreas Ziegler
2019-01-17 14:53 ` Steven Rostedt
2019-01-17 23:28 ` Masami Hiramatsu [this message]
2019-01-17 20:42 ` Joe Perches
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=20190118082837.6a4ff0668bf2d9e80846e454@kernel.org \
--to=mhiramat@kernel.org \
--cc=andreas.ziegler@fau.de \
--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).