Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754792AbYHGQLb (ORCPT ); Thu, 7 Aug 2008 12:11:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752700AbYHGQLX (ORCPT ); Thu, 7 Aug 2008 12:11:23 -0400 Received: from 136-022.dsl.labridge.com ([206.117.136.22]:4569 "EHLO mail.perches.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752668AbYHGQLW (ORCPT ); Thu, 7 Aug 2008 12:11:22 -0400 Subject: Re: [patch 1/3] kmsg: Kernel message catalog macros. From: Joe Perches To: schwidefsky@de.ibm.com Cc: Greg KH , Kay Sievers , linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, lf_kernel_messages@lists.linux-foundation.org, Andrew Morton , Michael Holzheu , Gerrit Huizenga , Randy Dunlap , Jan Kara , Pavel Machek , Sam Ravnborg , Jochen =?ISO-8859-1?Q?Vo=DF?= , Kunai Takashi , Tim Bird In-Reply-To: <1218097901.1033.10.camel@localhost> References: <20080730165656.118280544@de.ibm.com> <20080730171156.824640459@de.ibm.com> <3ae72650807301502h3e54e80yb405af7192048b89@mail.gmail.com> <20080730220432.GA24800@suse.de> <1217495404.8555.20.camel@localhost> <20080805223117.GA6552@suse.de> <1218011716.20769.12.camel@localhost> <20080806200721.GA30086@suse.de> <1218097901.1033.10.camel@localhost> Content-Type: text/plain Date: Thu, 07 Aug 2008 08:59:30 -0700 Message-Id: <1218124771.5882.37.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3-1.3mdv2008.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1268 Lines: 31 On Thu, 2008-08-07 at 10:31 +0200, Martin Schwidefsky wrote: > On Wed, 2008-08-06 at 13:07 -0700, Greg KH wrote: > > No, I mean use dev_printk() as the base for your logging macro. Add > > your message tag as the first field after the dev_printk() information. > Hmm, you are proposing to introduce a second format for the kmsg > messages to avoid the need for some more printk wrapper macros. To me it > seems that this has two problems: > 1) The message tag is for the user of the system. If it does not have a > fixed position it gets confusing. I think the message tag today is not useful for a user. It seems a barely useful maintainer value. Perhaps the message tag allows for run-time language translation and maybe a bit better selective logging. > 2) The message tag for a driver message usually already includes the > driver name, the dev_printk will print it again. This is ugly and > reduces the quality of the message. Ugly is a beholder problem. Either printk or dev_printk could reorder the output. -- 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/