lkml.org 
[lkml]   [2004]   [Dec]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: printk loglevel policy?
On Thu, 30 Dec 2004, Jim Nelson wrote:

> Coywolf Qi Hunt wrote:
> > Hi all,
> > Recently, I've seen a lot of add loglevel to printk patches. grep 'printk("'
> > -r | wc shows me 2433. There are probably 2433 printk
> > need to patch, is it? What's this printk loglevel policy, all these
> > printk calls need loglevel adjusted? The default loglevel is
> > KERN_WARNING.
> >
[...]
>
> The logging levels are, for the most part, common sense. KERN_ERR for error
> conditions, KERN_INFO for informational (i. e. "driver just loaded", "new disk
> detected"), KERN_CRIT if your computer just caught on fire (!), and KERN_DEBUG
> for any kind of verbose printing.
>
And the patches I've posted just try to set the loglevel to something
sensible where what is sensible seems to be obvious. If I'm right or wrong
I'll leave to the maintainers to decide.


--
Jesper Juhl



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:09    [W:0.047 / U:1.064 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site