[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1504026634.2040.27.camel@perches.com>
Date: Tue, 29 Aug 2017 10:10:34 -0700
From: Joe Perches <joe@...ches.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Pavel Machek <pavel@....cz>
Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>, Jan Kara <jack@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Jiri Slaby <jslaby@...e.com>, Andreas Mohr <andi@...as.de>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: printk: what is going on with additional newlines?
On Tue, 2017-08-29 at 09:48 -0700, Linus Torvalds wrote:
> On Mon, Aug 28, 2017 at 2:05 AM, Pavel Machek <pavel@....cz> wrote:
> > Hi!
> >
> > In 4.13-rc, printk("foo"); printk("bar"); seems to produce
> > foo\nbar. That's... quite surprising/unwelcome. What is going on
> > there? Are timestamps responsible?
>
> No.
>
> It's actively trying to treach you not to do shit.
>
> If you want to continue a line, you NEED to use KERN_CONT.
>
> That has always been true. It hasn't always been enforced, though.
That's simply false.
It was never true until you made it a requirement.
(it's not a bad requirement, but it did change behavior)
It was just unfortunate there were( and still are)
many cases that needed updating.
Powered by blists - more mailing lists