Hi Arjan, Thanks. I will check pr_debug() and family of APIs For dev(), it must do more changes and isn't the main purpose of this patch. This will be next patch.
-----Original Message----- From: Arjan van de Ven [mailto:[email protected]] Sent: Tuesday, June 14, 2011 11:08 PM To: Chang, Samuel Cc: Samuel Ortiz; Wu, Ricky; Huang, Maggie; [email protected]; Yang, Jack Subject: Re: [Meego-kernel] [PATCH] ar6003 : reduce unnecessary log during driver loading V2 On 6/14/2011 8:06 AM, Chang, Samuel wrote: > Hi Arjan, > > I checked with dev_err / dev_warn(). > The implementation of dev_err / dev_warn() is printk(KERN_ERR args) and > printk(KERN_WARNING args). actually that's a way oversimplification. there is a per device field that tools can enable to hide/enabling messages on a per device basis. it also provides a standardized format to that tools can filter messages coming from a device. > The reason I didn't use dev_err / dev_warn() is there is no suitable (or easy > to get) "dev" variable in ar6003 driver. > So, I need to put NULL for this dev variable. > Then dev_err will be printk(KERN_ERR "Null device" ...). then use pr_debug() and family of APIs but really you can get to a dev() normally... _______________________________________________ MeeGo-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
