[$] printk() indexing

When kernel developers want to communicate something about the state of arunning kernel, they tend to use printk(); that results in a logentry that is intended - with varying success - to be human-readable. As ithappens, though, theconsumers of that information are often not human; the kernel's log outputis also read by automated monitoring systems that are looking forproblems. The result is an impedance mismatch that often ends with themonitoring system missing important messages. The printk()format indexing patch set is the latest of many attempts to improvethis situation.