printk loglevel policy?

[Coywolf Qi Hunt <coywolf@gmail.com>]

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.


--coywolf



On Fri, 31 Dec 2004 03:02:57 +0100 (CET), Jesper Juhl <juhl-lkml@dif.dk> wrote:
> 
> Hi,
> 
> below is a small patch that adds loglevel to a printk in
> fs/afs/cmservice.c
> 
> If considered OK please consider applying.
> 
> Signed-off-by: Jesper Juhl <juhl-lkml@dif.dk>
> 
> diff -up linux-2.6.10-bk2-orig/fs/afs/cmservice.c linux-2.6.10-bk2/fs/afs/cmservice.c
> --- linux-2.6.10-bk2-orig/fs/afs/cmservice.c    2004-12-24 22:34:44.000000000 +0100
> +++ linux-2.6.10-bk2/fs/afs/cmservice.c 2004-12-31 02:59:13.000000000 +0100
> @@ -118,7 +118,7 @@ static int kafscmd(void *arg)
>         _SRXAFSCM_xxxx_t func;
>         int die;
> 
> -       printk("kAFS: Started kafscmd %d\n", current->pid);
> +       printk(KERN_INFO "kAFS: Started kafscmd %d\n", current->pid);
> 
>         daemonize("kafscmd");
> 
> -
> 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/
> 


-- 
Coywolf Qi Hunt
Homepage http://sosdg.org/~coywolf/