From: Adrian Hunter <adrian.hunter@intel.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
linux-perf-users@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] perf test: Fix spelling mistake "curent" -> "current"
Date: Mon, 26 Feb 2024 13:59:39 +0200 [thread overview]
Message-ID: <5a1ad9a5-52d8-4d78-9c26-ee5b9eb00b40@intel.com> (raw)
In-Reply-To: <20240226105326.3944887-1-colin.i.king@gmail.com>
On 26/02/24 12:53, Colin Ian King wrote:
> There is a spelling mistake in a pr_debug message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
> tools/perf/tests/symbols.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/tests/symbols.c b/tools/perf/tests/symbols.c
> index 2fed6d67f50f..d208105919ed 100644
> --- a/tools/perf/tests/symbols.c
> +++ b/tools/perf/tests/symbols.c
> @@ -85,7 +85,7 @@ static int create_map(struct test_info *ti, char *filename, struct map **map_p)
> *map_p = find_module_map(ti->machine, dso);
> dso__put(dso);
> if (!*map_p) {
> - pr_debug("Failed to find map for curent kernel module %s",
> + pr_debug("Failed to find map for current kernel module %s",
> filename);
> return TEST_FAIL;
> }
next prev parent reply other threads:[~2024-02-26 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 10:53 [PATCH][next] perf test: Fix spelling mistake "curent" -> "current" Colin Ian King
2024-02-26 11:59 ` Adrian Hunter [this message]
2024-02-27 17:27 ` Namhyung Kim
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=5a1ad9a5-52d8-4d78-9c26-ee5b9eb00b40@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=colin.i.king@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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).