Re: [patch 1/6] kmsg: tagged kernel messages.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2008-09-27 at 17:15 +1000, Rusty Russell wrote:
> > These are just the regular printk levels. If your old printk used a
> > particular level, have the kmsg_xxx printk use the same level. The
> > question about message severity and message documenation are
> > independent, aren't they?
> 
> Yes, but since it's a new message API, I thought you might have an idea.  It's 
> hard for authors (eg. me) to know which level to use.  As a result, levels 
> currently seem to be chosen randomly.
> 
> If you felt inspired to rationalize them, it would let us clean that up as 
> things moved to kmsg :)

Urgs, you are after a sort of definition what the differences is between
a warning, an error, an alert, etc is, aren't you?

-- 
blue skies,
  Martin.

"Reality continues to ruin my life." - Calvin.


--
To unsubscribe from this list: send the line "unsubscribe linux-s390" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Kernel Development]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Info]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Linux Media]     [Device Mapper]

  Powered by Linux