mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Luis Henriques <luis.henriques@canonical.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: fix typo in pr_warning() message
Date: Tue, 09 Sep 2014 15:20:13 -0700	[thread overview]
Message-ID: <1410301213.22675.4.camel@joe-AO725> (raw)
In-Reply-To: <1410299369-20029-1-git-send-email-luis.henriques@canonical.com>

On Tue, 2014-09-09 at 22:49 +0100, Luis Henriques wrote:
> Replace 'produciton' by 'production'
> 
> Signed-off-by: Luis Henriques <luis.henriques@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 8a528392b1f4..f3ef80c8914c 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -2028,7 +2028,7 @@ void trace_printk_init_buffers(void)
>  	pr_warning("** trace_printk() being used. Allocating extra memory.  **\n");
>  	pr_warning("**                                                      **\n");
>  	pr_warning("** This means that this is a DEBUG kernel and it is     **\n");
> -	pr_warning("** unsafe for produciton use.                           **\n");
> +	pr_warning("** unsafe for production use.                           **\n");
>  	pr_warning("**                                                      **\n");
>  	pr_warning("** If you see this message and you are not debugging    **\n");
>  	pr_warning("** the kernel, report this immediately to your vendor!  **\n");

Perhaps s/pr_warning/pr_warn/ too?



  reply	other threads:[~2014-09-09 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 21:49 Luis Henriques
2014-09-09 22:20 ` Joe Perches [this message]
2014-09-10  9:05   ` Luis Henriques
2014-09-10 14:06     ` Joe Perches

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=1410301213.22675.4.camel@joe-AO725 \
    --to=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.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®