Messages in this thread | | | Date | Thu, 14 Aug 2008 22:33:10 -0700 | From | "Tim Hockin" <> | Subject | Re: [patch 1/3] kmsg: Kernel message catalog macros. |
| |
On Thu, Aug 14, 2008 at 8:44 PM, Greg KH <gregkh@suse.de> wrote: > > What is wrong with what we have already agreed to standardise on here > people? dev_printk() for devices! It uniquely shows the device, what > driver is bound to it (if any), the bus id, and everything else.
Part of the problem, imho, is the "if any" part. But I am more than happy to build on existing solutions. All the world is not a dev, though. I'd like to be able to report something like an OOM kill in (roughly) the same way as an ATA error, and I want (though could be talked out of) a way to tell these "events" (for lack of a better word) apart from plain-old-printk()s.
Tim
| |