diff options
| author | Kay Sievers <kay@vrfy.org> | 2012-07-13 20:55:00 +0200 |
|---|---|---|
| committer | Kay Sievers <kay@vrfy.org> | 2012-07-13 20:55:00 +0200 |
| commit | 5daeb22bf3356982f1192c5de471d38762edcbce (patch) | |
| tree | f55aead1338a1219bdc164fd6ef83939e3f23397 | |
| parent | 67fb8cfdd24615ae2953f2e520cf09dfed710978 (diff) | |
| download | patches-5daeb22bf3356982f1192c5de471d38762edcbce.tar.gz | |
update changelog
| -rw-r--r-- | 03-kmsg-cont-order.patch | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/03-kmsg-cont-order.patch b/03-kmsg-cont-order.patch index 94d4a63..470b9b2 100644 --- a/03-kmsg-cont-order.patch +++ b/03-kmsg-cont-order.patch @@ -5,13 +5,13 @@ 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. -If the continuation line is complete and no part of it was written to the -console up to this point, we can just store the entire line as a regular -record and free the buffer earlier. +If the the console is busy and the continuation line is complete but no part +of it was written to the console up to this point, we can just store the +entire line as a regular record and free the buffer earlier. -If the console is busy and earlier messages are already held back, we -should not try flush fragments of continuation lines, but store them after -the queued up messages. +If the console is busy and earlier messages are already queued up, we +should not flush the fragments of continuation lines, but store them after +the queued up messages, to ensure the proper ordering. This keeps the console output better readable in case printk()s race against each other, or we receive over-long continuation lines we need to flush. |