Messages in this thread | | | Date | Tue, 5 Aug 2008 15:31:17 -0700 | From | Greg KH <> | Subject | Re: [patch 1/3] kmsg: Kernel message catalog macros. |
| |
On Thu, Jul 31, 2008 at 11:10:04AM +0200, Martin Schwidefsky wrote: > On Wed, 2008-07-30 at 15:04 -0700, Greg KH wrote: > > On Thu, Jul 31, 2008 at 12:02:04AM +0200, Kay Sievers wrote: > > > On Wed, Jul 30, 2008 at 18:56, Martin Schwidefsky > > > <schwidefsky@de.ibm.com> wrote: > > > > > > > +#define kmsg_dev_alert(id, dev, format, arg...) \ > > > > + printk(__KMSG_CHECK(ALERT, id) KMSG_COMPONENT \ > > > > + ": %s: " format, (dev)->bus_id , ## arg) > > > > > > Care to use dev_name(), bus_id will be removed soon. > > > > Hm, just use dev_printk() instead, it handles all of these kinds of > > changes automatically. > > Using dev_printk won't work because of the order of the elements of the > printk. The kmsg tag should not have a "random" position in the printk > but should be the first element. If we use dev_printk the kmsg tag will > be the third element, for other kmsg printks it will be the first. In > addition the kmsg message tag for the device drivers already includes > the driver name ..
But the structure of dev_printk() is well definied and should be pretty trival to parse even with missing fields.
And if not, fix up dev_printk() to properly delinate when we have missing fields, why create a totally new thing here that we need to convert subsystems into?
thanks,
greg k-h
| |