From: David Ahern <dsahern@gmail.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [TRIVIAL] perf probe usability related fixes.
Date: Fri, 20 Jan 2012 07:47:11 -0700 [thread overview]
Message-ID: <4F197E6F.5070003@gmail.com> (raw)
In-Reply-To: <20120120121354.GL15447@linux.vnet.ibm.com>
On 01/20/2012 05:13 AM, Srikar Dronamraju wrote:
> From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
>
> Ingo pointed out few perf probe usability related errors during
> his review of uprobes.
>
> Since these issues are independent of uprobes, fixing them in a
> separate patch.
>
> Suggested-by: Ingo Molnar <mingo@elte.hu>
> Signed-off-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> ---
> tools/perf/util/probe-event.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
> index f6f5794..da38ec5 100644
> --- a/tools/perf/util/probe-event.c
> +++ b/tools/perf/util/probe-event.c
> @@ -1825,7 +1825,7 @@ static int __add_probe_trace_events(struct perf_probe_event *pev,
> }
>
> ret = 0;
> - printf("Add new event%s\n", (ntevs > 1) ? "s:" : ":");
> + printf("Added new event%s\n", (ntevs > 1) ? "s:" : ":");
It's not past tense until after write_probe_trace_event() right? Where
the message is now you can get an error message after that printf.
David
next prev parent reply other threads:[~2012-01-20 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 12:13 [PATCH] [TRIVIAL] perf probe usability related fixes Srikar Dronamraju
2012-01-20 14:47 ` David Ahern [this message]
2012-01-24 0:27 ` Masami Hiramatsu
2012-01-26 13:35 ` [tip:perf/core] perf probe: Usability fixes tip-bot for Srikar Dronamraju
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=4F197E6F.5070003@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=srikar@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.