public inbox for linux-kernel@vger.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 1/5] perf script: Fix outdated comment for perf-trace-python
Date: Wed, 7 Jun 2017 20:19:04 -0300	[thread overview]
Message-ID: <20170607231904.GC6949@kernel.org> (raw)
In-Reply-To: <20170530111827.21732-2-sj38.park@gmail.com>

Em Tue, May 30, 2017 at 08:18:23PM +0900, SeongJae Park escreveu:
> Script that generated by '--gen-script' option contains an outdated
> comment.  It mentions about 'perf-trace-python' document while it has
> renamed to 'perf-script-python'.  This commit fixes the outdated
> comment.

Thanks, applied to perf/urgent.

- Arnaldo
 
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
> Fixes: 133dc4c39c57 ("perf: Rename 'perf trace' to 'perf script'")
> ---
>  tools/perf/util/scripting-engines/trace-event-python.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/util/scripting-engines/trace-event-python.c b/tools/perf/util/scripting-engines/trace-event-python.c
> index 9d92af7d0718..40de3cb40d21 100644
> --- a/tools/perf/util/scripting-engines/trace-event-python.c
> +++ b/tools/perf/util/scripting-engines/trace-event-python.c
> @@ -1219,7 +1219,7 @@ static int python_generate_script(struct pevent *pevent, const char *outfile)
>  	fprintf(ofp, "# be retrieved using Python functions of the form "
>  		"common_*(context).\n");
>  
> -	fprintf(ofp, "# See the perf-trace-python Documentation for the list "
> +	fprintf(ofp, "# See the perf-script-python Documentation for the list "
>  		"of available functions.\n\n");
>  
>  	fprintf(ofp, "import os\n");
> -- 
> 2.13.0

  reply	other threads:[~2017-06-07 23:19 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 [this message]
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
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=20170607231904.GC6949@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox