lkml.org 
[lkml]   [2011]   [Jul]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] printk: add Kconfig for default console loglevel
On Tue, Jul 26, 2011 at 10:01:45AM -0700, Joe Perches wrote:
> On Tue, 2011-07-26 at 09:37 -0700, Randy Dunlap wrote:
> > On Tue, 26 Jul 2011 11:33:51 -0400 Dave Reisner wrote:
> > > Keep the historical default of 7, but allow distributions and users to
> > > tune this value instead of requiring a kernel cmdline parameter.
> > Please explain how this is different from what is already in lib/Kconfig.debug:
> > config DEFAULT_MESSAGE_LOGLEVEL
> > int "Default message log level (1-7)"
> > range 1 7
> > default "4"
> > help
> > Default log level for printk statements with no specified priority.
>
> DEFAULT_MESSAGE_LOGLEVEL sets a KERN_<level> for
> printks without a KERN_<level>.
>
> > > +config DEFAULT_CONSOLE_LOGLEVEL
> > > + int "Default console log level (1-7)"
> > > + range 1 7
> > > + default "7"
> > > + help
> > > + Default console log level setting for printk statements.
> > > +
> > > + This was hard-coded to KERN_INFO (7) since at least 2.6.12. You may
> > > + wish to turn this down to 4 for a quieter console.
> > > +
>
> This allows 'unimportant' messages to not be shown by default.
>
> I think there are lots of KERN_INFO messages that are
> miscategorized. This change might cause some shifting
> of KERN_<level>s in the future, so it's OK by me.
>

Joe,

Did you want me to resubmit with your addition? Do I need to cc anyone
else to move this along to Linus's integration branch? Apologies, my
familiarity with the merge process for the kernel stops at the
documentation in the git repo.

dave


\
 
 \ /
  Last update: 2011-07-29 15:01    [W:0.074 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site