From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: Remove newline from trace_printk warning banner
Date: Tue, 27 Jan 2015 12:05:58 -0500 [thread overview]
Message-ID: <20150127120558.0b428aac@gandalf.local.home> (raw)
In-Reply-To: <1422375440-31970-1-git-send-email-bp@alien8.de>
On Tue, 27 Jan 2015 17:17:20 +0100
Borislav Petkov <bp@alien8.de> wrote:
> From: Borislav Petkov <bp@suse.de>
>
> Remove the output-confusing newline below:
>
> [ 0.191328]
> **********************************************************
> [ 0.191493] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
> [ 0.191586] ** **
> ...
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> ---
> 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 4a9079b9f082..7a04946ffb06 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -2036,7 +2036,7 @@ void trace_printk_init_buffers(void)
>
> /* trace_printk() is for debug use only. Don't use it in production. */
>
> - pr_warning("\n**********************************************************\n");
> + pr_warning("**********************************************************\n");
Actually, could you just move the \n to another pr_warning. Because
this can print on console text that makes it look weird too:
login: [ 0.191328] **********************************************************
[ 0.191493] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
[ 0.191586] ** **
-- Steve
> pr_warning("** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **\n");
> pr_warning("** **\n");
> pr_warning("** trace_printk() being used. Allocating extra memory. **\n");
prev parent reply other threads:[~2015-01-27 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 16:17 Borislav Petkov
2015-01-27 17:05 ` Steven Rostedt [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=20150127120558.0b428aac@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bp@alien8.de \
--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 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®