From: Namhyung Kim <namhyung@kernel.org>
To: Masanari Iida <standby24x7@gmail.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 1/2] [trivial] tools: perf: Fix typo in tools/perf
Date: Wed, 18 Jul 2012 11:15:27 +0900 [thread overview]
Message-ID: <87eho93jcw.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1342542059-9756-1-git-send-email-standby24x7@gmail.com> (Masanari Iida's message of "Wed, 18 Jul 2012 01:20:59 +0900")
Hi, Masanari
On Wed, 18 Jul 2012 01:20:59 +0900, Masanari Iida wrote:
> Correct spelling typo in tools/perf.
>
> Signed-off-by: Masanari iida <standby24x7@gmail.com>
> ---
> tools/perf/util/callchain.h | 2 +-
> tools/perf/util/parse-events-test.c | 2 +-
> tools/perf/util/python-ext-sources | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/util/callchain.h b/tools/perf/util/callchain.h
> index 3bdb407..eb34057 100644
> --- a/tools/perf/util/callchain.h
> +++ b/tools/perf/util/callchain.h
> @@ -58,7 +58,7 @@ struct callchain_list {
> /*
> * A callchain cursor is a single linked list that
> * let one feed a callchain progressively.
> - * It keeps persitent allocated entries to minimize
> + * It keeps persistent allocated entries to minimize
s/persistent/persistently/ ?
Thanks,
Namhyung
> * allocations.
> */
> struct callchain_cursor_node {
> diff --git a/tools/perf/util/parse-events-test.c b/tools/perf/util/parse-events-test.c
> index 76b98e2..8cdf147 100644
> --- a/tools/perf/util/parse-events-test.c
> +++ b/tools/perf/util/parse-events-test.c
> @@ -609,7 +609,7 @@ static int test_pmu(void)
>
> ret = stat(path, &st);
> if (ret)
> - pr_debug("ommiting PMU cpu tests\n");
> + pr_debug("omitting PMU cpu tests\n");
> return !ret;
> }
>
> diff --git a/tools/perf/util/python-ext-sources b/tools/perf/util/python-ext-sources
> index 2884e67..f4e37ce 100644
> --- a/tools/perf/util/python-ext-sources
> +++ b/tools/perf/util/python-ext-sources
> @@ -1,5 +1,5 @@
> #
> -# List of files needed by perf python extention
> +# List of files needed by perf python extension
> #
> # Each source file must be placed on its own line so that it can be
> # processed by Makefile and util/setup.py accordingly.
next prev parent reply other threads:[~2012-07-18 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 16:20 Masanari Iida
2012-07-18 2:15 ` Namhyung Kim [this message]
2012-07-18 16:35 ` [PATCH v2] " 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=87eho93jcw.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=standby24x7@gmail.com \
--cc=trivial@kernel.org \
/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
all inboxes | Powered by JetHome®