[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1341877262.6118.73.camel@joe2Laptop>
Date: Mon, 09 Jul 2012 16:41:02 -0700
From: Joe Perches <joe@...ches.com>
To: Kay Sievers <kay@...y.org>
Cc: Michael Neuling <mikey@...ling.org>, linuxppc-dev@...abs.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Wu Fengguang <fengguang.wu@...el.com>,
"Paul E. McKenney" <paulmck@...ibm.com>
Subject: Re: [PATCH v3] printk: Have printk() never buffer its data
On Mon, 2012-07-09 at 16:32 -0700, Joe Perches wrote:
> Then you've changed semantics and I think you need to
> fix it.
>
> A dev_<level> call is not guaranteed to be a complete
> message.
>
> There are dev_<level> and netdev_<level> calls
> followed by pr_cont.
>
> Maybe these could be fixed up and then they could be
> always integral. There don't look to be too many.
>
> This may be most (all?) of them:
Nah, there's a bunch more:
$ git grep -E -A10 "\b(netdev|dev)_(info|warn|notice|err|alert|emerg|crit)" drivers | \
grep -B10 -E "\bprintk\s*\(\s*(KERN_CONT|)\s*\""
All of them could be fixed up though.
--
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