[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070614094128.GF17819@atrey.karlin.mff.cuni.cz>
Date: Thu, 14 Jun 2007 11:41:28 +0200
From: Jan Kara <jack@...e.cz>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: holzheu@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
randy.dunlap@...cle.com, gregkh@...e.de, mtk-manpages@....net,
schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
"lf_kernel_messages@...ux-foundation.org"
<lf_kernel_messages@...ux-foundation.org>
Subject: Re: [RFC/PATCH] Documentation of kernel messages
<snip>
> Your proposal is similar to one I made to some Japanese developers
> earlier this year. I was more modest, proposing that we
>
> - add an enhanced printk
>
> xxprintk(msgid, KERN_ERR "some text %d\n", some_number);
Maybe a stupid idea but why do we want to assign these numbers by hand?
I can imagine it could introduce collisions when merging tons of patches
with new messages... Wouldn't it be better to compute say, 8-byte hash
from the message and use it as it's identifier? We could do this
automagically at compile time. I know it also has it's problems - you
fix a spelling and the message gets a different id and you have to
update translation/documentation catalogue but maybe that could be
solved too...
Honza
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists