[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070618133311.GK9319@duck.suse.cz>
Date: Mon, 18 Jun 2007 15:33:11 +0200
From: Jan Kara <jack@...e.cz>
To: Arjan van de Ven <arjan@...radead.org>
Cc: holzheu@...ux.vnet.ibm.com, Gerrit Huizenga <gh@...ibm.com>,
Jan Kara <jack@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
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
On Mon 18-06-07 06:12:54, Arjan van de Ven wrote:
> On Mon, 2007-06-18 at 14:55 +0200, holzheu wrote:
> > 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....
I think the problem is messages contain device numbers, and all similar
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@...e.cz>
SuSE CR Labs
-
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