From: Namhyung Kim <namhyung@kernel.org>
To: Sangwon Hong <qpakzk@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Taeung Song <treeze.taeung@gmail.com>,
kernel-team@lge.com
Subject: Re: [PATCH 2/2] perf mem: Document a missing option
Date: Mon, 12 Feb 2018 10:51:59 +0900 [thread overview]
Message-ID: <20180212015159.GD31513@sejong> (raw)
In-Reply-To: <1518381517-30766-2-git-send-email-qpakzk@gmail.com>
On Mon, Feb 12, 2018 at 05:38:37AM +0900, Sangwon Hong wrote:
> Add the missing --force option on the man page.
>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Taeung Song <treeze.taeung@gmail.com>
> Signed-off-by: Sangwon Hong <qpakzk@gmail.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
> ---
> tools/perf/Documentation/perf-mem.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/tools/perf/Documentation/perf-mem.txt b/tools/perf/Documentation/perf-mem.txt
> index 4be08a1..b021141 100644
> --- a/tools/perf/Documentation/perf-mem.txt
> +++ b/tools/perf/Documentation/perf-mem.txt
> @@ -28,6 +28,10 @@ OPTIONS
> <command>...::
> Any command you can specify in a shell.
>
> +-f::
> +--force::
> + Don't do ownership validation
> +
> -t::
> --type=::
> Select the memory operation type: load or store (default: load,store)
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-02-12 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 20:38 [PATCH 1/2] perf kmem: Document a missing option & an argument Sangwon Hong
2018-02-11 20:38 ` [PATCH 2/2] perf mem: Document a missing option Sangwon Hong
2018-02-12 1:51 ` Namhyung Kim [this message]
2018-02-17 11:31 ` [tip:perf/core] " tip-bot for Sangwon Hong
2018-02-12 1:51 ` [PATCH 1/2] perf kmem: Document a missing option & an argument Namhyung Kim
2018-02-15 15:01 ` Arnaldo Carvalho de Melo
2018-02-17 11:31 ` [tip:perf/core] " tip-bot for Sangwon Hong
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=20180212015159.GD31513@sejong \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qpakzk@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).