From: SeongJae Park <sj38.park@gmail.com>
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com
Cc: linux-kernel@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 1/5] perf script: Fix outdated comment for perf-trace-python
Date: Tue, 30 May 2017 20:18:23 +0900 [thread overview]
Message-ID: <20170530111827.21732-2-sj38.park@gmail.com> (raw)
In-Reply-To: <20170530111827.21732-1-sj38.park@gmail.com>
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.
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
next prev parent reply other threads:[~2017-05-30 11: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 ` SeongJae Park [this message]
2017-06-07 23:19 ` [PATCH 1/5] perf script: Fix outdated comment for perf-trace-python 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
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=20170530111827.21732-2-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).