From: Randy Dunlap <rdunlap@infradead.org>
To: Masanari Iida <standby24x7@gmail.com>,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
paulus@samba.org, mingo@redhat.com, acme@kernel.org
Subject: Re: [PATCH/v2] perf/documentation: Fix typo in perf/Documentation
Date: Wed, 03 Sep 2014 10:02:48 -0700 [thread overview]
Message-ID: <540749B8.5090302@infradead.org> (raw)
In-Reply-To: <1409715963-513-1-git-send-email-standby24x7@gmail.com>
On 09/02/14 20:46, Masanari Iida wrote:
> This patch fix spelling typo found in tool/perf/Documentation.
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Sorry, I found a few more items that could be fixed...
and I seem to have mucked up yesterday's comments. :(
> ---
> tools/perf/Documentation/perf-diff.txt | 6 +++---
> tools/perf/Documentation/perf-kvm.txt | 4 ++--
> tools/perf/Documentation/perf-list.txt | 2 +-
> tools/perf/Documentation/perf-record.txt | 2 +-
> tools/perf/Documentation/perf-script-perl.txt | 4 ++--
> tools/perf/Documentation/perf-script-python.txt | 6 +++---
> tools/perf/Documentation/perf-script.txt | 2 +-
> tools/perf/Documentation/perf-test.txt | 2 +-
> tools/perf/Documentation/perf-trace.txt | 2 +-
> 9 files changed, 15 insertions(+), 15 deletions(-)
>
> diff --git a/tools/perf/Documentation/perf-kvm.txt b/tools/perf/Documentation/perf-kvm.txt
> index 6e689dc..4edbc2b 100644
> --- a/tools/perf/Documentation/perf-kvm.txt
> +++ b/tools/perf/Documentation/perf-kvm.txt
> @@ -100,7 +100,7 @@ OPTIONS
> STAT REPORT OPTIONS
> -------------------
> --vcpu=<value>::
> - analyze events which occures on this vcpu. (default: all vcpus)
> + analyze events which occurs on this vcpu. (default: all vcpus)
occur
>
> --event=<value>::
> event to be analyzed. Possible values: vmexit, mmio (x86 only),
> @@ -134,7 +134,7 @@ STAT LIVE OPTIONS
> Analyze events only for given process ID(s) (comma separated list).
>
> --vcpu=<value>::
> - analyze events which occures on this vcpu. (default: all vcpus)
> + analyze events which occurs on this vcpu. (default: all vcpus)
occur
>
>
> --event=<value>::
> diff --git a/tools/perf/Documentation/perf-test.txt b/tools/perf/Documentation/perf-test.txt
> index d1d3e5121..9fc5c5d 100644
> --- a/tools/perf/Documentation/perf-test.txt
> +++ b/tools/perf/Documentation/perf-test.txt
> @@ -25,7 +25,7 @@ OPTIONS
> -------
> -s::
> --skip::
> - Tests to skip (comma separater numeric list).
> + Tests to skip (comma separator numeric list).
separated
>
> -v::
> --verbose::
> diff --git a/tools/perf/Documentation/perf-trace.txt b/tools/perf/Documentation/perf-trace.txt
> index 02aac83..524c169 100644
> --- a/tools/perf/Documentation/perf-trace.txt
> +++ b/tools/perf/Documentation/perf-trace.txt
> @@ -20,7 +20,7 @@ scheduling events, etc.
> This is a live mode tool in addition to working with perf.data files like
> the other perf tools. Files can be generated using the 'perf record' command
> but the session needs to include the raw_syscalls events (-e 'raw_syscalls:*').
> -Alernatively, the 'perf trace record' can be used as a shortcut to
> +Alternatively, the 'perf trace record' can be used as a shortcut to
either:
the 'perf trace record' command can be used ...
or
'perf trace record' can be used ...
> automatically include the raw_syscalls events when writing events to a file.
>
> The following options apply to perf trace; options to perf trace record are
>
Thanks.
--
~Randy
next prev parent reply other threads:[~2014-09-03 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 3:46 [PATCH] " Masanari Iida
2014-09-02 16:18 ` Randy Dunlap
2014-09-03 3:46 ` [PATCH/v2] " Masanari Iida
2014-09-03 17:02 ` Randy Dunlap [this message]
2014-09-09 15:18 ` [PATCH/v3] " Masanari Iida
2014-09-09 20:46 ` Randy Dunlap
2014-10-15 19:30 ` Arnaldo Carvalho de Melo
2014-10-16 5:24 ` [tip:perf/urgent] perf Documentation: Fix typos in perf/ Documentation tip-bot for Masanari Iida
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=540749B8.5090302@infradead.org \
--to=rdunlap@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=standby24x7@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