Mandeep Singh Baines 5af5bcb8d3 printk: allow setting DEFAULT_MESSAGE_LEVEL via Kconfig
We've been burned by regressions/bugs which we later realized could have
been triaged quicker if only we'd paid closer attention to dmesg.  To make
it easier to audit dmesg, we'd like to make DEFAULT_MESSAGE_LEVEL
Kconfig-settable.  That way we can set it to KERN_NOTICE and audit any
messages <= KERN_WARNING.

Signed-off-by: Mandeep Singh Baines <msb@chromium.org>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Joe Perches <joe@perches.com>
Cc: Olof Johansson <olofj@chromium.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2011-03-22 17:44:13 -07:00
..
2010-10-26 16:52:18 -07:00
2009-11-03 16:06:53 +01:00
2010-07-11 22:16:32 +02:00
2009-01-01 10:12:19 +10:30
2009-06-18 13:04:05 -07:00
2010-05-25 08:07:06 -07:00
2010-04-06 15:52:11 -07:00
2010-08-09 20:45:05 -07:00
2010-11-22 13:25:13 +10:00
2009-10-01 21:17:49 +02:00
2010-10-26 16:52:19 -07:00
2011-03-11 15:14:48 -05:00
2010-06-16 18:08:13 +02:00
2010-01-11 09:34:05 -08:00
2010-03-06 11:26:35 -08:00
2011-02-25 15:07:36 -08:00
2010-05-19 22:40:47 -04:00