On Wed, Jun 8, 2011 at 12:37 PM, Chang, Samuel <[email protected]> wrote: > Hi Auke, > > Could you suggest which kind of debug message function is correct for > meego.kernel rule ?
I'm not entirely sure what you mean by this, but you should look at using: dev_err() and family. See include/linux/device.h, around line 550: 561 #define dev_emerg(dev, format, arg...) \ 562 dev_printk(KERN_EMERG , dev , format , ## arg) 563 #define dev_alert(dev, format, arg...) \ 564 dev_printk(KERN_ALERT , dev , format , ## arg) 565 #define dev_crit(dev, format, arg...) \ 566 dev_printk(KERN_CRIT , dev , format , ## arg) 567 #define dev_err(dev, format, arg...) \ 568 dev_printk(KERN_ERR , dev , format , ## arg) 569 #define dev_warn(dev, format, arg...) \ 570 dev_printk(KERN_WARNING , dev , format , ## arg) 571 #define dev_notice(dev, format, arg...) \ 572 dev_printk(KERN_NOTICE , dev , format , ## arg) 573 #define dev_info(dev, format, arg...) \ 574 dev_printk(KERN_INFO , dev , format , ## arg) 575 576 #if defined(DEBUG) 577 #define dev_dbg(dev, format, arg...) \ 578 dev_printk(KERN_DEBUG , dev , format , ## arg) etc... these work properly and should solve the issue. Auke _______________________________________________ MeeGo-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
