printk: update changelog

1 files changed, 16 insertions, 15 deletions

diff --git a/printk.patch b/printk.patch
index 09870ce..8c300f4 100644
--- a/printk.patch
+++ b/printk.patch
@@ -1,23 +1,24 @@
 From: Kay Sievers <kay@vrfy.org>
-Subject: [WORK-IN-PROGRESS] printk: support structured and multi-facility log messages
+Subject: printk: support structured and multi-facility log messages
 
 The kernel messages are the primary source of information about the overall
-state of the system and its connected hardware. The usual kernel messages are
-mostly un-formatted plain text, targeted at a human reading them. That goal
-works very well since a very long time.
+state of the system and the connected device. The usual kernel messages are
+mostly human language, targeted at a person reading them. That part of the
+picture works very well since a very long time.
 
-Most machines though, run unattended, and software and not humans needs to read
-the messages. Having a machine making sense out of human readable messages is
-inefficient, unreliable, or sometimes plain impossible to get right. All the
-useful information about the context available at the time of creation of the
-message is thrown away. Later consumers of the messages will need to apply
-magic to guess what the context might have been, which was thrown way.
+Most machines though, run unattended almost all of their time, and software
+needs, and not humans, to read the kernel messages. Having a machine making
+sense out of human language messages is inefficient, unreliable, or sometimes
+plain impossible to get right. All the useful information about the context
+available at the time of creation of the message, is just thrown away. Later,
+consumers of the messages will need to apply magic to guess what the context
+might have been, to interpret the messages.
 
-This extends printk to be able to attach key/value pairs to the log messages,
-to carry machine-readable key/values to describe the context of the log
-at time of creation. Users of the log can retrieve, along with the
-human-readable message, the key/value dictionary to reliably identify specific
-devices, drivers, subsystems, classes and types of messages.
+This extends printk() to be able to attach arbitrary key/value pairs to the
+log messages, to carry machine-readable data to describe the context of the
+log message at time of its creation. Users of the log can retrieve, along with
+the human-readable message, a key/value dictionary to reliably identify
+specific devices, drivers, subsystems, classes and types of messages.
 
 - Record-based instead of byte-stream buffer. All records carry proper
   timestamp, syslog facility, priority in the record header.