[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D41DC42.3070603@bluewatersys.com>
Date: Fri, 28 Jan 2011 09:57:38 +1300
From: Ryan Mallon <ryan@...ewatersys.com>
To: Alexey Dobriyan <adobriyan@...il.com>
CC: Mandeep Singh Baines <msb@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Randy Dunlap <rdunlap@...otime.net>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
olofj@...omium.org
Subject: Re: [PATCH] printk: allow setting DEFAULT_MESSAGE_LEVEL via Kconfig
On 01/28/2011 09:53 AM, Alexey Dobriyan wrote:
> On Fri, Jan 28, 2011 at 09:45:23AM +1300, Ryan Mallon wrote:
>> Why not make printk prefix messages that have no log level with
>> "[NO_LOG_LEVEL]" or similar? That way the can easily be grepped out, and
>> it provides and incentive for people to fix them :-).
>
> Because printk("foo"); ... printk("\n"); is legit.
It should be fixed to KERN_CONT should it not?
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan@...ewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists