tree 2dcf9d0557488349f4753838b6c689986dcf536c
parent 5e467652ffefb84b1159d5d8fda665c48e5fd840
author Linus Torvalds <torvalds@linux-foundation.org> 1476040617 -0700
committer Linus Torvalds <torvalds@linux-foundation.org> 1476041020 -0700

printk: make reading the kernel log flush pending lines

That will mean that any possible subsequent continuation will now be
broken up onto a line of its own (since reading the log has finalized
the beginning og the line), but if user space has activated system
logging (or if there's a kernel message dump going on) that is the right
thing to do.

And now that we actually get the continuation flags _right_ for this
all, the user space logger that is reading the kernel messages can
actually see the continuation marker.  Not that anybody seems to really
bother with it (or care), but in theory user space can do its own
message stitching.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>