linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: trivial@kernel.org
Cc: Colin King <colin.king@canonical.com>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: fix spelling mistake: "preapre" -> "prepare"
Date: Thu, 9 Nov 2017 20:52:44 -0500	[thread overview]
Message-ID: <20171109205244.30fb7687@vmware.local.home> (raw)
In-Reply-To: <20170429214848.11548-1-colin.king@canonical.com>


Cleaning out my indox, I discovered this patch. And it doesn't look
like it was applied.

Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

-- Steve


On Sat, 29 Apr 2017 22:48:48 +0100
Colin King <colin.king@canonical.com> wrote:

> From: Colin Ian King <colin.king@canonical.com>
> 
> trivial fix to spelling mistake in message.
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.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 beecf3f67159..76ab1d185322 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -8062,7 +8062,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,
>  				      NULL);
>  	if (ret < 0)
>  		goto out_free_cpumask;

  reply	other threads:[~2017-11-10  1:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29 21:48 [PATCH] tracing: fix spelling mistake: "preapre" -> "prepare" Colin King
2017-11-10  1:52 ` Steven Rostedt [this message]
2022-09-28 21:58 [PATCH] tracing: Fix spelling mistake " Colin Ian King
2022-09-28 22:13 ` 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=20171109205244.30fb7687@vmware.local.home \
    --to=rostedt@goodmis.org \
    --cc=colin.king@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=trivial@kernel.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).