From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Naohiro Aota <naota@elisp.net>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
namhyung@kernel.org, Jiri Olsa <jolsa@redhat.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH perf/core v3 0/3] perf-probe bugfixes
Date: Tue, 16 Jun 2015 10:48:44 -0300 [thread overview]
Message-ID: <20150616134844.GD10374@kernel.org> (raw)
In-Reply-To: <20150616115050.19906.77371.stgit@localhost.localdomain>
Em Tue, Jun 16, 2015 at 08:50:50PM +0900, Masami Hiramatsu escreveu:
> Hi Arnaldo,
>
> Here is the v3 series of bugfix patches for perf-probe.
> I've rewriten the patch description of 2/3 (no code changed)
> and added a comment on the 3/3 for reproductivity.
> This series fixes below bugs;
>
> - --list shows the list of probes in stderr.
> (It is refined from https://lkml.org/lkml/2015/5/30/34)
> - return success even if no probe is added.
> - usage message is not shown if the last event is skipped.
>
> BTW, this series still include 1/3, since I couldn't find it
> in the latest(published) perf/core. If you've already merged
> it on your local tree, please skip it.
Right, I forgot to push my perf/core branch yesterday, thanks for the
corrections, trying to apply the series now.
- Arnaldo
> Thank you,
>
> ---
>
> Masami Hiramatsu (3):
> [BUGFIX] perf probe: List probes in stdout
> [BUGFIX] perf probe: Fix to return error if no-probe is added
> [BUGFIX] perf probe: Show usage even if the last event is skipped
>
>
> tools/perf/util/probe-event.c | 187 ++++++++++++++++++++++++++---------------
> 1 file changed, 118 insertions(+), 69 deletions(-)
>
>
> --
> Masami HIRAMATSU
> Linux Technology Research Center, System Productivity Research Dept.
> Center for Technology Innovation - Systems Engineering
> Hitachi, Ltd., Research & Development Group
> E-mail: masami.hiramatsu.pt@hitachi.com
prev parent reply other threads:[~2015-06-16 13:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 11:50 [PATCH perf/core v3 0/3] perf-probe bugfixes Masami Hiramatsu
2015-06-16 11:50 ` [PATCH perf/core v3 1/3] [BUGFIX] perf probe: List probes in stdout Masami Hiramatsu
2015-06-16 11:50 ` [PATCH perf/core v3 2/3] [BUGFIX] perf probe: Fix to return error if no-probe is added Masami Hiramatsu
2015-06-18 8:15 ` [tip:perf/core] perf probe: Fix to return error if no probe " tip-bot for Masami Hiramatsu
2015-06-16 11:50 ` [PATCH perf/core v3 3/3] [BUGFIX] perf probe: Show usage even if the last event is skipped Masami Hiramatsu
2015-06-16 14:46 ` Arnaldo Carvalho de Melo
2015-06-17 5:31 ` Masami Hiramatsu
2015-06-17 14:58 ` Masami Hiramatsu
2015-06-17 14:58 ` [PATCH perf/core ] perf probe: Speed up perf probe --list by caching debuginfo Masami Hiramatsu
2015-06-18 8:17 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2015-06-17 15:00 ` Re: [PATCH perf/core v3 3/3] [BUGFIX] perf probe: Show usage even if the last event is skipped Arnaldo Carvalho de Melo
2015-06-18 8:16 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2015-06-16 13:48 ` Arnaldo Carvalho de Melo [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=20150616134844.GD10374@kernel.org \
--to=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=naota@elisp.net \
--cc=peterz@infradead.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