From: tip-bot for Sihyeon Jang <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: acme@redhat.com, mingo@kernel.org, namhyung@kernel.org,
tglx@linutronix.de, jolsa@kernel.org,
linux-kernel@vger.kernel.org, hpa@zytor.com,
uneedsihyeon@gmail.com
Subject: [tip:perf/core] perf inject: Document missing options
Date: Sat, 18 Nov 2017 00:37:21 -0800 [thread overview]
Message-ID: <tip-52186b8aa40f06350b33f8e4031879d389e2b9f2@git.kernel.org> (raw)
In-Reply-To: <1510842367-11011-1-git-send-email-uneedsihyeon@gmail.com>
Commit-ID: 52186b8aa40f06350b33f8e4031879d389e2b9f2
Gitweb: https://git.kernel.org/tip/52186b8aa40f06350b33f8e4031879d389e2b9f2
Author: Sihyeon Jang <uneedsihyeon@gmail.com>
AuthorDate: Thu, 16 Nov 2017 23:26:02 +0900
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Thu, 16 Nov 2017 14:50:05 -0300
perf inject: Document missing options
Add the missing --force option to the man page.
Signed-off-by: Sihyeon Jang <uneedsihyeon@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Link: http://lkml.kernel.org/r/1510842367-11011-1-git-send-email-uneedsihyeon@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/Documentation/perf-inject.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tools/perf/Documentation/perf-inject.txt b/tools/perf/Documentation/perf-inject.txt
index 87b2588..a64d658 100644
--- a/tools/perf/Documentation/perf-inject.txt
+++ b/tools/perf/Documentation/perf-inject.txt
@@ -60,6 +60,10 @@ include::itrace.txt[]
found in the jitdumps files captured in the input perf.data file. Use this option
if you are monitoring environment using JIT runtimes, such as Java, DART or V8.
+-f::
+--force::
+ Don't complain, do it.
+
SEE ALSO
--------
linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-archive[1]
prev parent reply other threads:[~2017-11-18 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 14:26 [PATCH 1/6] perf inject: Document missing options Sihyeon Jang
2017-11-16 14:26 ` [PATCH 2/6] perf trace: Document missing option, colons Sihyeon Jang
2017-11-18 8:37 ` [tip:perf/core] " tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 3/6] perf timechart: Document missing option Sihyeon Jang
2017-11-18 8:38 ` [tip:perf/core] perf timechart: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 4/6] perf sched: Document missing option Sihyeon Jang
2017-11-18 8:38 ` [tip:perf/core] perf sched: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 5/6] perf evlist: Document missing option Sihyeon Jang
2017-11-18 8:38 ` [tip:perf/core] perf evlist: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 6/6] perf buildid-cache: Document missing option Sihyeon Jang
2017-11-18 8:39 ` [tip:perf/core] perf buildid-cache: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:35 ` [PATCH 1/6] perf inject: Document missing options Arnaldo Carvalho de Melo
2017-11-18 8:37 ` tip-bot for Sihyeon Jang [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=tip-52186b8aa40f06350b33f8e4031879d389e2b9f2@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=uneedsihyeon@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