From: tip-bot for Sangwon Hong <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: acme@redhat.com, mingo@kernel.org, hpa@zytor.com,
treeze.taeung@gmail.com, linux-kernel@vger.kernel.org,
namhyung@kernel.org, jolsa@kernel.org, tglx@linutronix.de,
qpakzk@gmail.com
Subject: [tip:perf/urgent] perf data: Document missing --force option
Date: Fri, 16 Feb 2018 01:43:02 -0800 [thread overview]
Message-ID: <tip-ba7e851642f48002def3450b279598c187721fd0@git.kernel.org> (raw)
In-Reply-To: <1517831315-31490-1-git-send-email-qpakzk@gmail.com>
Commit-ID: ba7e851642f48002def3450b279598c187721fd0
Gitweb: https://git.kernel.org/tip/ba7e851642f48002def3450b279598c187721fd0
Author: Sangwon Hong <qpakzk@gmail.com>
AuthorDate: Mon, 5 Feb 2018 20:48:35 +0900
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Thu, 15 Feb 2018 09:57:33 -0300
perf data: Document missing --force option
Add the --force option to the man page.
Signed-off-by: Sangwon Hong <qpakzk@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Taeung Song <treeze.taeung@gmail.com>
Link: http://lkml.kernel.org/r/1517831315-31490-1-git-send-email-qpakzk@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/Documentation/perf-data.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tools/perf/Documentation/perf-data.txt b/tools/perf/Documentation/perf-data.txt
index f0796a4..90bb4aa 100644
--- a/tools/perf/Documentation/perf-data.txt
+++ b/tools/perf/Documentation/perf-data.txt
@@ -30,6 +30,10 @@ OPTIONS for 'convert'
-i::
Specify input perf data file path.
+-f::
+--force::
+ Don't complain, do it.
+
-v::
--verbose::
Be more verbose (show counter open errors, etc).
prev parent reply other threads:[~2018-02-16 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 11:48 [PATCH] perf annotate: " Sangwon Hong
2018-02-13 12:12 ` [tip:perf/urgent] perf data: " tip-bot for Sangwon Hong
2018-02-16 9:43 ` tip-bot for Sangwon Hong [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-ba7e851642f48002def3450b279598c187721fd0@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=qpakzk@gmail.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome