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

From: Sergey Senozhatsky
Date: Mon Sep 04 2017 - 00:33:54 EST


On (09/01/17 10:32), Joe Perches wrote:
[..]
> > +static inlin __printf(2, 3) __cold
>
> uncompiled
>
> > +static int __prbuf_write(struct seq_buf *s, const char *fmt, ...)
>
> inline
>

thanks.

there is always a missing

if (console_trylock())
console_unlock();

in flush() function.

-ss