From: Yang Jihong <yangjihong1@huawei.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>,
Mark Rutland <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
<linux-perf-users@vger.kernel.org>
Cc: <kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] perf kwork: Fix spelling mistake "Captuer" -> "Capture"
Date: Thu, 28 Jul 2022 19:57:03 +0800 [thread overview]
Message-ID: <a4aab976-d930-612c-38cb-b6f413f3654e@huawei.com> (raw)
In-Reply-To: <20220727124126.222137-1-colin.i.king@gmail.com>
Hello Colin,
On 2022/7/27 20:41, 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>
> ---
> tools/perf/builtin-kwork.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/builtin-kwork.c b/tools/perf/builtin-kwork.c
> index fb8c63656ad8..d5906e939756 100644
> --- a/tools/perf/builtin-kwork.c
> +++ b/tools/perf/builtin-kwork.c
> @@ -1447,7 +1447,7 @@ static void sig_handler(int sig)
> * Simply capture termination signal so that
> * the program can continue after pause returns
> */
> - pr_debug("Captuer signal %d\n", sig);
> + pr_debug("Capture signal %d\n", sig);
> }
>
> static int perf_kwork__report_bpf(struct perf_kwork *kwork)
>
OK, I'll fix in next patch,thanks for your review.
Regards,
Jihong
.
next prev parent reply other threads:[~2022-07-28 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 12:41 Colin Ian King
2022-07-28 11:57 ` Yang Jihong [this message]
2023-09-25 5:50 Colin Ian King
2023-09-25 16:08 ` Ian Rogers
2023-09-28 3:52 ` 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=a4aab976-d930-612c-38cb-b6f413f3654e@huawei.com \
--to=yangjihong1@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=colin.i.king@gmail.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
all inboxes | Powered by JetHome®