Messages in this thread | | | Date | Wed, 13 Aug 2008 00:04:11 -0700 | From | "Tim Hockin" <> | Subject | Re: [patch 1/3] kmsg: Kernel message catalog macros. |
| |
But there are a number of places that have different strings for the same meaning: "Can't" vs "can't" vs "can not" vs "failed to", etc.
This is a big part of what hurts us - you end up with lots of loose regexes when parsing logs.
Tim
On Tue, Aug 12, 2008 at 9:33 PM, Rusty Russell <rusty@rustcorp.com.au> wrote: > On Thursday 31 July 2008 02:56:57 Martin Schwidefsky wrote: >> From: Michael Holzheu <holzheu@de.ibm.com> >> From: Martin Schwidefsky <schwidefsky@de.ibm.com> >> >> Introduce a new family of printk macros which prefixes each kmsg message >> with a component name and allows to tag the printk with a message id. > > Can you hash the format string to generate the id? 6 hex digits should be > enough, and your tool can check for clashes. As it's bad form to have > identical strings for different semantics anyway, this seems to make sense. > > Rusty. > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >
| |