From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
kernel-janitors@vger.kernel.org,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kprobes: fix typo in comment
Date: Sun, 22 May 2022 00:28:26 +0900 [thread overview]
Message-ID: <20220522002826.b1afffb4d70b0be5c0dce363@kernel.org> (raw)
In-Reply-To: <20220521111145.81697-63-Julia.Lawall@inria.fr>
On Sat, 21 May 2022 13:11:13 +0200
Julia Lawall <Julia.Lawall@inria.fr> wrote:
> Spelling mistake (triple letters) in comment.
> Detected with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
Looks good to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thank you!
>
> ---
> kernel/kprobes.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index dd58c0be9ce2..4721b76e61a1 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -651,7 +651,7 @@ void wait_for_kprobe_optimizer(void)
> while (!list_empty(&optimizing_list) || !list_empty(&unoptimizing_list)) {
> mutex_unlock(&kprobe_mutex);
>
> - /* This will also make 'optimizing_work' execute immmediately */
> + /* This will also make 'optimizing_work' execute immediately */
> flush_delayed_work(&optimizing_work);
> /* 'optimizing_work' might not have been queued yet, relax */
> cpu_relax();
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2022-05-21 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 11:11 [PATCH] kprobes: fix typo in comment Julia Lawall
2022-05-21 15:28 ` Masami Hiramatsu [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=20220522002826.b1afffb4d70b0be5c0dce363@kernel.org \
--to=mhiramat@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
/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).