Subject: Re: [RFC/PATCH] Documentation of kernel messages
From: Dave Hansen <hansendc@us.ibm.com>
To: Greg KH <gregkh@suse.de>
Cc: holzheu <holzheu@linux.vnet.ibm.com>, linux-kernel@vger.kernel.org,
       randy.dunlap@oracle.com, akpm@osdl.org, mtk-manpages@gmx.net,
       schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com
In-Reply-To: <20070613183200.GA16588@suse.de>
References: <1181747217.29512.9.camel@localhost.localdomain>
	 <20070613175147.GB14355@suse.de>
	 <1181758680.26375.25.camel@localhost.localdomain>
	 <20070613183200.GA16588@suse.de>
Content-Type: text/plain
Date: Wed, 13 Jun 2007 11:49:15 -0700
Message-Id: <1181760555.8735.17.camel@spirit>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 872
Lines: 24

On Wed, 2007-06-13 at 11:32 -0700, Greg KH wrote:
> 
> > dev_printk() and friends are great, since they already define
> something
> > like KMSG_COMPONENT: The driver name.
> 
> They provide way more than that, they also provide the explicit device
> that is being discussed, as well as other things depending on the
> device. 

Instead of keeping a list of kernel message ids somewhere, can you base
this off the dev_printk() format argument?

You could keep a list of those somewhere, extracted from the kernel
source, and correlate documentation with the _format_ instead of an
arbitrarily assigned message number.

-- Dave

-
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/