Re: [RFC/PATCH] Documentation of kernel messages
- From: Jan Kara <jack@xxxxxxx>
- Date: Mon, 18 Jun 2007 15:33:11 +0200
On Mon 18-06-07 06:12:54, Arjan van de Ven wrote:
On Mon, 2007-06-18 at 14:55 +0200, holzheu wrote:I think the problem is messages contain device numbers, and all similar
Hi Gerrit,
The common thing of your and our approach is, that we need an ID to
identify a message either by:
Maybe I am missing something big, but why is an ID needed?
The message IS the ID right? That's the only thing that is robust
against code moving about....
kind of data. So what you'd really like is to use >format string< as ID.
But that is not easily accessible for the user, so you'd have to print it
with each message. And that's ... ugly IMHO.
(And yes I am aware that very occasionally there might be a duplicate
message that REALLY is different, but I suspect that that is so
incredibly rare that it's just simpler to reword one of the two in such
case)
Honza
--
Jan Kara <jack@xxxxxxx>
SuSE CR Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: [RFC/PATCH] Documentation of kernel messages
- From: Gerrit Huizenga
- Re: [RFC/PATCH] Documentation of kernel messages
- From: holzheu
- Re: [RFC/PATCH] Documentation of kernel messages
- From: Arjan van de Ven
- Re: [RFC/PATCH] Documentation of kernel messages
- Prev by Date: Re: [RFC/PATCH] Documentation of kernel messages
- Next by Date: RE: How to improve the quality of the kernel?
- Previous by thread: Re: [RFC/PATCH] Documentation of kernel messages
- Next by thread: Re: [RFC/PATCH] Documentation of kernel messages
- Index(es):
Relevant Pages
|