Messages in this thread | | | From | Rusty Russell <> | Subject | Re: [patch 1/6] kmsg: tagged kernel messages. | Date | Fri, 26 Sep 2008 14:48:04 +1000 |
| |
On Friday 26 September 2008 02:28:28 Martin Schwidefsky wrote: > +#define kmsg_emerg(fmt, ...) \ > + kmsg_printk_hash(KERN_EMERG, fmt, ##__VA_ARGS__) > +#define kmsg_alert(fmt, ...) \ > + kmsg_printk_hash(KERN_ALERT, fmt, ##__VA_ARGS__) > +#define kmsg_crit(fmt, ...) \ > + kmsg_printk_hash(KERN_CRIT, fmt, ##__VA_ARGS__) > +#define kmsg_err(fmt, ...) \ > + kmsg_printk_hash(KERN_ERR, fmt, ##__VA_ARGS__) > +#define kmsg_warn(fmt, ...) \ > + kmsg_printk_hash(KERN_WARNING, fmt, ##__VA_ARGS__) > +#define kmsg_notice(fmt, ...) \ > + kmsg_printk_hash(KERN_NOTICE, fmt, ##__VA_ARGS__) > +#define kmsg_info(fmt, ...) \ > + kmsg_printk_hash(KERN_INFO, fmt, ##__VA_ARGS__)
Now I'm going to be an asshole and ask you to define when each of these levels should be used. Do we need all of them?
Thanks, Rusty.
| |