All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: SeongJae Park <sj38.park@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] perf-script-python.txt: Fix wrong code snippets
Date: Wed, 7 Jun 2017 20:35:23 -0300	[thread overview]
Message-ID: <20170607233523.GF6949@kernel.org> (raw)
In-Reply-To: <20170530111827.21732-5-sj38.park@gmail.com>

Em Tue, May 30, 2017 at 08:18:26PM +0900, SeongJae Park escreveu:
> This commit fixes wrong code snippets for trace_begin() and trace_end()
> function example definition.

Fixed, and using:

  git log --follow tools/perf/Documentation/perf-script-python.txt

Added the Fixes: tag:

Fixes: cff68e582237 ("perf/scripts: Add perf-trace-python Documentation")

And since you're taking the time to add the Fixes tag (yay, great!)
please also add Cc: entries for the patch author and committer, in that
case:

Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>

I did it this time, using a script I have:

[acme@jouet linux]$ cat ~/bin/fixes 
#!/bin/bash

cset=$1
if [ $# -eq 0 ] ; then
	read cset
fi
git show --pretty=fuller $cset | grep '^\(Author\|Commit\): ' | sed -r 's/.*: +/Cc: /g'
echo Fixes: `git one $cset`
[acme@jouet linux]$

Just get the cset, in vim, and select it, pressing Shift+V while the
cursor is on top of the cset id and then press : and finally !fixes +
ENTER :)

cff68e582237

- Arnaldo
 
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
> ---
>  tools/perf/Documentation/perf-script-python.txt | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/perf/Documentation/perf-script-python.txt b/tools/perf/Documentation/perf-script-python.txt
> index 44e51351536f..f723ce41268c 100644
> --- a/tools/perf/Documentation/perf-script-python.txt
> +++ b/tools/perf/Documentation/perf-script-python.txt
> @@ -530,7 +530,7 @@ can implement a set of optional functions:
>  gives scripts a chance to do setup tasks:
>  
>  ----
> -def trace_begin:
> +def trace_begin():
>      pass
>  ----
>  
> @@ -539,7 +539,7 @@ def trace_begin:
>   as display results:
>  
>  ----
> -def trace_end:
> +def trace_end():
>      pass
>  ----
>  
> -- 
> 2.13.0

  reply	other threads:[~2017-06-07 23:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 11:18 [PATCH 0/5] perf: Fix few nitpicks in perf-script SeongJae Park
2017-05-30 11:18 ` [PATCH 1/5] perf script: Fix outdated comment for perf-trace-python SeongJae Park
2017-06-07 23:19   ` Arnaldo Carvalho de Melo
2017-06-08 22:46   ` [tip:perf/urgent] " tip-bot for SeongJae Park
2017-05-30 11:18 ` [PATCH 2/5] perf-script-python,perl.txt: Fix typos SeongJae Park
2017-06-07 23:19   ` Arnaldo Carvalho de Melo
2017-06-08 22:47   ` [tip:perf/urgent] perf script: Fix documentation errors tip-bot for SeongJae Park
2017-05-30 11:18 ` [PATCH 3/5] perf-script-python.txt: Polish command examples SeongJae Park
2017-06-08 22:49   ` [tip:perf/urgent] perf script python: Remove dups in documentation examples tip-bot for SeongJae Park
2017-05-30 11:18 ` [PATCH 4/5] perf-script-python.txt: Fix wrong code snippets SeongJae Park
2017-06-07 23:35   ` Arnaldo Carvalho de Melo [this message]
2017-06-07 23:47     ` SeongJae Park
2017-06-08 22:47   ` [tip:perf/urgent] perf script python: Fix wrong code snippets in documentation tip-bot for SeongJae Park
2017-05-30 11:18 ` [PATCH 5/5] perf-script-python.txt: Apply updated trace_unhandled() definition SeongJae Park
2017-06-07 23:27   ` Arnaldo Carvalho de Melo
2017-06-08 22:48   ` [tip:perf/urgent] perf script python: Updated trace_unhandled() signature tip-bot for SeongJae Park
2017-06-07 22:42 ` [PATCH 0/5] perf: Fix few nitpicks in perf-script 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=20170607233523.GF6949@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sj38.park@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.