All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Colin King <colin.king@canonical.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] ftrace: fix spelling mistake "wakeing" -> "waking"
Date: Fri, 15 Nov 2019 10:54:56 -0500	[thread overview]
Message-ID: <20191115105456.29444b06@gandalf.local.home> (raw)
In-Reply-To: <20191115085938.38947-1-colin.king@canonical.com>

On Fri, 15 Nov 2019 08:59:38 +0000
Colin King <colin.king@canonical.com> wrote:

> From: Colin Ian King <colin.king@canonical.com>
> 
> There is a spelling mistake in a trace_printk message. Fix it.

As this breaks the selftests, I'm folding this patch into the one that
you sent that updates the selftests as well.

-- Steve

> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  samples/ftrace/ftrace-direct.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/samples/ftrace/ftrace-direct.c b/samples/ftrace/ftrace-direct.c
> index 1483f067b000..a2e3063bd306 100644
> --- a/samples/ftrace/ftrace-direct.c
> +++ b/samples/ftrace/ftrace-direct.c
> @@ -6,7 +6,7 @@
>  
>  void my_direct_func(struct task_struct *p)
>  {
> -	trace_printk("wakeing up %s-%d\n", p->comm, p->pid);
> +	trace_printk("waking up %s-%d\n", p->comm, p->pid);
>  }
>  
>  extern void my_tramp(void *);


WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Colin King <colin.king@canonical.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] ftrace: fix spelling mistake "wakeing" -> "waking"
Date: Fri, 15 Nov 2019 15:54:56 +0000	[thread overview]
Message-ID: <20191115105456.29444b06@gandalf.local.home> (raw)
In-Reply-To: <20191115085938.38947-1-colin.king@canonical.com>

On Fri, 15 Nov 2019 08:59:38 +0000
Colin King <colin.king@canonical.com> wrote:

> From: Colin Ian King <colin.king@canonical.com>
> 
> There is a spelling mistake in a trace_printk message. Fix it.

As this breaks the selftests, I'm folding this patch into the one that
you sent that updates the selftests as well.

-- Steve

> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  samples/ftrace/ftrace-direct.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/samples/ftrace/ftrace-direct.c b/samples/ftrace/ftrace-direct.c
> index 1483f067b000..a2e3063bd306 100644
> --- a/samples/ftrace/ftrace-direct.c
> +++ b/samples/ftrace/ftrace-direct.c
> @@ -6,7 +6,7 @@
>  
>  void my_direct_func(struct task_struct *p)
>  {
> -	trace_printk("wakeing up %s-%d\n", p->comm, p->pid);
> +	trace_printk("waking up %s-%d\n", p->comm, p->pid);
>  }
>  
>  extern void my_tramp(void *);

  reply	other threads:[~2019-11-15 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15  8:59 [PATCH][next] ftrace: fix spelling mistake "wakeing" -> "waking" Colin King
2019-11-15 15:54 ` Steven Rostedt [this message]
2019-11-15 15:54   ` Steven Rostedt
2019-11-15 15:55   ` Colin Ian King

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=20191115105456.29444b06@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=colin.king@canonical.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.