summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKay Sievers <kay@vrfy.org>2012-07-13 15:54:48 +0200
committerKay Sievers <kay@vrfy.org>2012-07-13 15:54:48 +0200
commit954674b4e1e09170e620d1554fae3daaf069b0ef (patch)
tree4a14344207e3b3cd0db829a89c387db89c33477a
parent89404808b4b9c560cf32cd7353884bc2c542e71c (diff)
downloadpatches-954674b4e1e09170e620d1554fae3daaf069b0ef.tar.gz
add changelog to kmsg-cont-order.patch
-rw-r--r--03-kmsg-cont-order.patch19
1 files changed, 19 insertions, 0 deletions
diff --git a/03-kmsg-cont-order.patch b/03-kmsg-cont-order.patch
index dcf3d78..fd7755c 100644
--- a/03-kmsg-cont-order.patch
+++ b/03-kmsg-cont-order.patch
@@ -1,4 +1,23 @@
+From: Kay Sievers <kay@vrfy.org>
+Subject: kmsg - do not flush partial lines when the console is busy
+
+Fragments of continuation lines are flushed to the console immediately. In
+case the console is locked the fragment must be queued up in the cont
+buffer.
+
+When the continuation line is complete and no part of it was written to the
+console up to this point, we just store the entire line as record.
+
+If the console is busy and other messages are still queued up, we should not
+try flush fragments of continuation lines, but sort them after the queued
+up messages.
+
+This keeps the console output better readable in case we receive over-long
+continuation lines we need to flush.
+
+Signed-off-by: Kay Sievers <kay@vrfy.org>
---
+
kernel/printk.c | 89 ++++++++++++++++++++++++++++++++++++++++----------------
1 file changed, 64 insertions(+), 25 deletions(-)