Re: printk: what is going on with additional newlines?

Joe Perches
2017-08-29T17:10:39Z

On Tue, 2017-08-29 at 09:48 -0700, Linus Torvalds wrote:
> On Mon, Aug 28, 2017 at 2:05 AM, Pavel Machek <pavel@ucw.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.