lkml.org 
[lkml]   [2008]   [Sep]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [patch 1/6] kmsg: tagged kernel messages.
Date
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.


\
 
 \ /
  Last update: 2008-09-26 06:51    [from the cache]
©2003-2011 Jasper Spaans. Advertise on this site