From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: SeongJae Park <sj38.park@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Taeung Song <treeze.taeung@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf probe: Fix examples section of documentation
Date: Mon, 8 May 2017 13:30:52 -0300 [thread overview]
Message-ID: <20170508163052.GH7891@kernel.org> (raw)
In-Reply-To: <20170509001957.9e6458593fc1b8e9b344761d@kernel.org>
Em Tue, May 09, 2017 at 12:19:57AM +0900, Masami Hiramatsu escreveu:
> On Sun, 7 May 2017 19:36:42 +0900
> SeongJae Park <sj38.park@gmail.com> wrote:
>
> > An example in perf-probe documentation for pattern of function name
> > based probe addition is not providing example command for the case.
> > This commit fixes the example to give appropriate example command.
> >
> > Signed-off-by: SeongJae Park <sj38.park@gmail.com>
>
> Good catch!
>
> Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thanks, I added the suggested Fixes: tag,
- Arnaldo
> Thank you!
>
> > ---
> > tools/perf/Documentation/perf-probe.txt | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/perf/Documentation/perf-probe.txt b/tools/perf/Documentation/perf-probe.txt
> > index e6c9902c6d82..165c2b1d4317 100644
> > --- a/tools/perf/Documentation/perf-probe.txt
> > +++ b/tools/perf/Documentation/perf-probe.txt
> > @@ -240,9 +240,13 @@ Add a probe on schedule() function 12th line with recording cpu local variable:
> > or
> > ./perf probe --add='schedule:12 cpu'
> >
> > - this will add one or more probes which has the name start with "schedule".
> > +Add one or more probes which has the name start with "schedule".
> >
> > - Add probes on lines in schedule() function which calls update_rq_clock().
> > + ./perf probe schedule*
> > + or
> > + ./perf probe --add='schedule*'
> > +
> > +Add probes on lines in schedule() function which calls update_rq_clock().
> >
> > ./perf probe 'schedule;update_rq_clock*'
> > or
> > --
> > 2.12.0
> >
>
>
> --
> Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2017-05-08 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 10:36 [PATCH] perf probe: Fix examples section of documentation SeongJae Park
2017-05-08 8:12 ` Taeung Song
2017-05-08 15:19 ` Masami Hiramatsu
2017-05-08 16:30 ` Arnaldo Carvalho de Melo [this message]
2017-06-08 22:46 ` [tip:perf/urgent] " tip-bot for SeongJae Park
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=20170508163052.GH7891@kernel.org \
--to=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sj38.park@gmail.com \
--cc=treeze.taeung@gmail.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.