From: Mukesh Ojha <mojha@codeaurora.org>
To: Colin King <colin.king@canonical.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf test: fix spelling mistake "allos" -> "allocate"
Date: Tue, 17 Sep 2019 13:12:46 +0530 [thread overview]
Message-ID: <2b525705-317a-29a7-9fda-ca7896c8c038@codeaurora.org> (raw)
In-Reply-To: <20190911152148.17031-1-colin.king@canonical.com>
On 9/11/2019 8:51 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a TEST_ASSERT_VAL message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Thanks,
Mukesh
> ---
> tools/perf/tests/event_update.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/tests/event_update.c b/tools/perf/tests/event_update.c
> index cac4290e233a..7f0868a31a7f 100644
> --- a/tools/perf/tests/event_update.c
> +++ b/tools/perf/tests/event_update.c
> @@ -92,7 +92,7 @@ int test__event_update(struct test *test __maybe_unused, int subtest __maybe_unu
>
> evsel = perf_evlist__first(evlist);
>
> - TEST_ASSERT_VAL("failed to allos ids",
> + TEST_ASSERT_VAL("failed to allocate ids",
> !perf_evsel__alloc_id(evsel, 1, 1));
>
> perf_evlist__id_add(evlist, evsel, 0, 0, 123);
next prev parent reply other threads:[~2019-09-17 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 15:21 [PATCH] perf test: fix spelling mistake "allos" -> "allocate" Colin King
2019-09-17 7:42 ` Mukesh Ojha [this message]
2019-09-18 23:09 ` Arnaldo Carvalho de Melo
2019-09-20 16:20 ` [tip: perf/urgent] perf test: Fix " tip-bot2 for Colin Ian King
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=2b525705-317a-29a7-9fda-ca7896c8c038@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=colin.king@canonical.com \
--cc=jolsa@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).