linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Fix spelling mistake "preapre" -> "prepare"
Date: Wed, 28 Sep 2022 18:13:32 -0400	[thread overview]
Message-ID: <20220928181332.5819a8cc@gandalf.local.home> (raw)
In-Reply-To: <20220928215828.66325-1-colin.i.king@gmail.com>

On Wed, 28 Sep 2022 22:58:28 +0100
Colin Ian King <colin.i.king@gmail.com> wrote:

> There is a spelling mistake in the trace text. Fix it.
> 
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
>  kernel/trace/trace.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index d3005279165d..623c5691ab21 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -10091,7 +10091,7 @@ __init static int tracer_alloc_buffers(void)
>  	 * buffer. The memory will be removed once the "instance" is removed.
>  	 */
>  	ret = cpuhp_setup_state_multi(CPUHP_TRACE_RB_PREPARE,
> -				      "trace/RB:preapre", trace_rb_cpu_prepare,
> +				      "trace/RB:prepare", trace_rb_cpu_prepare,

This is exposed to user space. Hopefully nobody is depending on it ;-)

>  				      NULL);
>  	if (ret < 0)
>  		goto out_free_cpumask;


I'll risk the breakage. Thanks.

-- Steve

  reply	other threads:[~2022-09-28 22:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 21:58 [PATCH] tracing: Fix spelling mistake "preapre" -> "prepare" Colin Ian King
2022-09-28 22:13 ` Steven Rostedt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-04-29 21:48 [PATCH] tracing: fix spelling mistake: " Colin King
2017-11-10  1:52 ` Steven Rostedt

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=20220928181332.5819a8cc@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=colin.i.king@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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).