From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf header: Fix spelling mistake "could't" -> "couldn't"
Date: Tue, 22 Mar 2022 18:27:26 -0300 [thread overview]
Message-ID: <Yjo/PvaJQSuQ5xKA@kernel.org> (raw)
In-Reply-To: <20220316232212.52820-1-colin.i.king@gmail.com>
Em Wed, Mar 16, 2022 at 11:22:11PM +0000, Colin Ian King escreveu:
> There is a spelling mistake in a pr_debug2 message. Fix it.
Thanks, applied.
- Arnaldo
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> tools/perf/util/header.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> index 6da12e522edc..4a44a0740f43 100644
> --- a/tools/perf/util/header.c
> +++ b/tools/perf/util/header.c
> @@ -1335,7 +1335,7 @@ static int build_mem_topology(struct memory_node *nodes, u64 size, u64 *cntp)
>
> dir = opendir(path);
> if (!dir) {
> - pr_debug2("%s: could't read %s, does this arch have topology information?\n",
> + pr_debug2("%s: couldn't read %s, does this arch have topology information?\n",
> __func__, path);
> return -1;
> }
> --
> 2.35.1
--
- Arnaldo
prev parent reply other threads:[~2022-03-22 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 23:22 [PATCH] perf header: Fix spelling mistake "could't" -> "couldn't" Colin Ian King
2022-03-17 3:09 ` Ian Rogers
2022-03-22 21:27 ` Arnaldo Carvalho de Melo [this message]
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=Yjo/PvaJQSuQ5xKA@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@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).