Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764996AbXFST2g (ORCPT ); Tue, 19 Jun 2007 15:28:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763852AbXFST2a (ORCPT ); Tue, 19 Jun 2007 15:28:30 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:58536 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761040AbXFST23 (ORCPT ); Tue, 19 Jun 2007 15:28:29 -0400 Subject: Re: [RFC/PATCH] Documentation of kernel messages From: Arjan van de Ven To: holzheu@linux.vnet.ibm.com Cc: Gerrit Huizenga , Jan Kara , Andrew Morton , linux-kernel@vger.kernel.org, randy.dunlap@oracle.com, gregkh@suse.de, mtk-manpages@gmx.net, schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, "lf_kernel_messages@linux-foundation.org" , pavel@ucw.cz In-Reply-To: <1182243088.11540.2.camel@localhost.localdomain> References: <1182171354.11400.40.camel@localhost.localdomain> <1182172374.28566.1.camel@laptopd505.fenrus.org> <1182174836.11400.64.camel@localhost.localdomain> <1182216982.3014.1.camel@laptopd505.fenrus.org> <1182243088.11540.2.camel@localhost.localdomain> Content-Type: text/plain Organization: Intel International BV Date: Tue, 19 Jun 2007 12:24:52 -0700 Message-Id: <1182281097.2698.0.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 (2.10.2-2.fc7) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1570 Lines: 39 On Tue, 2007-06-19 at 10:51 +0200, holzheu wrote: > On Mon, 2007-06-18 at 18:36 -0700, Arjan van de Ven wrote: > > On Mon, 2007-06-18 at 15:53 +0200, holzheu wrote: > > > On Mon, 2007-06-18 at 06:12 -0700, 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.... > > > > > > Yes. As already discussed with Pavel, it is one option to use the format > > > string of the message as message ID. The disadvantage compared to > > > message IDs like hashes is, that format strings might be even less > > > unique than hashes > > > > if the hash comes from the string in the first place I have a hard time > > believing that. > > > > Just think of all messages containing %s, which can expand to every > possible string. of course you hash on the string before you do the format stuff.... -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org - 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/