On Fri, Oct 7, 2016 at 4:01 PM, Tony Luck <tony.l...@gmail.com> wrote: > What if there isn't a "next printk" call for hours, or days? > > That poor little message without a "\n" will sit in the kernel buffers, > and the user who might want to see the message can't, until some > unrelated thing happens to print something.
Retracted ... I'm sure that at some point in the past it happened like that ... but I just retested on 4.8 and the first message (with no "\n") showed up on the serial port just fine without some other message to push it out. When the next message came along, a "\n" was auto-inserted. -Tony