All of lore.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Sihyeon Jang <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jolsa@kernel.org, mingo@kernel.org,
	tglx@linutronix.de, namhyung@kernel.org, hpa@zytor.com,
	uneedsihyeon@gmail.com, acme@redhat.com
Subject: [tip:perf/core] perf buildid-cache: Document missing --force option
Date: Sat, 18 Nov 2017 00:39:21 -0800	[thread overview]
Message-ID: <tip-5a79eef4eccf0571e856eb13c0ffe19083d27474@git.kernel.org> (raw)
In-Reply-To: <1510842367-11011-6-git-send-email-uneedsihyeon@gmail.com>

Commit-ID:  5a79eef4eccf0571e856eb13c0ffe19083d27474
Gitweb:     https://git.kernel.org/tip/5a79eef4eccf0571e856eb13c0ffe19083d27474
Author:     Sihyeon Jang <uneedsihyeon@gmail.com>
AuthorDate: Thu, 16 Nov 2017 23:26:07 +0900
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Thu, 16 Nov 2017 14:50:07 -0300

perf buildid-cache: Document missing --force option

Add --force 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-6-git-send-email-uneedsihyeon@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 tools/perf/Documentation/perf-buildid-cache.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tools/perf/Documentation/perf-buildid-cache.txt b/tools/perf/Documentation/perf-buildid-cache.txt
index 8468100..73c2650 100644
--- a/tools/perf/Documentation/perf-buildid-cache.txt
+++ b/tools/perf/Documentation/perf-buildid-cache.txt
@@ -24,6 +24,9 @@ OPTIONS
 -a::
 --add=::
         Add specified file to the cache.
+-f::
+--force::
+	Don't complain, do it.
 -k::
 --kcore::
         Add specified kcore file to the cache. For the current host that is

  reply	other threads:[~2017-11-18  8:41 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-bot for Sihyeon Jang [this message]
2017-11-16 14:35 ` [PATCH 1/6] perf inject: Document missing options Arnaldo Carvalho de Melo
2017-11-18  8:37 ` [tip:perf/core] " tip-bot for Sihyeon Jang

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-5a79eef4eccf0571e856eb13c0ffe19083d27474@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 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.