From: Randy Dunlap <rdunlap@infradead.org>
To: Borislav Petkov <bp@alien8.de>, LKML <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
x86@kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
Jason Wessel <jason.wessel@windriver.com>,
kgdb-bugreport@lists.sourceforge.net,
Hedi Berriche <hedi@sgi.com>, Mike Travis <travis@sgi.com>,
Dimitri Sivanich <sivanich@sgi.com>,
Steven Rostedt <rostedt@goodmis.org>,
Kees Cook <keescook@chromium.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] printk: Use symbolic defines for console loglevels
Date: Mon, 19 May 2014 13:38:40 -0700 [thread overview]
Message-ID: <537A6BD0.9010504@infradead.org> (raw)
In-Reply-To: <1400524052-25625-1-git-send-email-bp@alien8.de>
On 05/19/2014 11:27 AM, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
>
> ... instead of naked numbers.
>
> Stuff in sysrq.c used to set it to 8 which is supposed to mean above
> default level so set it to DEBUG instead as we're terminating/killing
> all tasks and we want to be verbose there.
>
> There should be no functionality change resulting from this patch.
>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: x86@kernel.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Jiri Slaby <jslaby@suse.cz>
> Cc: Jason Wessel <jason.wessel@windriver.com>
> Cc: kgdb-bugreport@lists.sourceforge.net
> Cc: Hedi Berriche <hedi@sgi.com>
> Cc: Mike Travis <travis@sgi.com>
> Cc: Dimitri Sivanich <sivanich@sgi.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> ---
> arch/x86/kernel/head64.c | 2 +-
> arch/x86/platform/uv/uv_nmi.c | 2 +-
> drivers/nubus/nubus.c | 18 +++++++++---------
> drivers/tty/sysrq.c | 8 ++++----
> include/linux/printk.h | 15 +++++++++++++--
> init/main.c | 4 ++--
> kernel/debug/kdb/kdb_bt.c | 2 +-
> kernel/debug/kdb/kdb_io.c | 2 +-
> kernel/debug/kdb/kdb_main.c | 2 +-
> kernel/printk/printk.c | 13 +++----------
> 10 files changed, 36 insertions(+), 32 deletions(-)
--
~Randy
next prev parent reply other threads:[~2014-05-19 20:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 18:27 [PATCH] printk: Use symbolic defines for console loglevels Borislav Petkov
2014-05-19 19:12 ` Joe Perches
2014-05-19 19:25 ` Borislav Petkov
2014-05-19 19:36 ` Kees Cook
2014-05-19 20:38 ` Randy Dunlap [this message]
2014-05-20 5:44 ` Valdis.Kletnieks
2014-05-27 19:17 ` Steven Rostedt
2014-05-27 19:43 ` Borislav Petkov
2014-05-27 22:36 ` Valdis.Kletnieks
2014-05-27 22:59 ` Borislav Petkov
2014-05-27 23:26 ` Andrew Morton
2014-05-27 23:32 ` Steven Rostedt
2014-05-27 23:43 ` Borislav Petkov
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=537A6BD0.9010504@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hedi@sgi.com \
--cc=jason.wessel@windriver.com \
--cc=jslaby@suse.cz \
--cc=keescook@chromium.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sivanich@sgi.com \
--cc=torvalds@linux-foundation.org \
--cc=travis@sgi.com \
--cc=x86@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