Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754158AbYGaJL2 (ORCPT ); Thu, 31 Jul 2008 05:11:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752499AbYGaJLS (ORCPT ); Thu, 31 Jul 2008 05:11:18 -0400 Received: from mtagate6.de.ibm.com ([195.212.29.155]:42878 "EHLO mtagate6.de.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751239AbYGaJLR (ORCPT ); Thu, 31 Jul 2008 05:11:17 -0400 Subject: Re: [patch 1/3] kmsg: Kernel message catalog macros. From: Martin Schwidefsky Reply-To: schwidefsky@de.ibm.com To: Greg KH Cc: 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 , Joe Perches , Jochen =?ISO-8859-1?Q?Vo=DF?= , Kunai Takashi , Tim Bird In-Reply-To: <20080730220432.GA24800@suse.de> References: <20080730165656.118280544@de.ibm.com> <20080730171156.824640459@de.ibm.com> <3ae72650807301502h3e54e80yb405af7192048b89@mail.gmail.com> <20080730220432.GA24800@suse.de> Content-Type: text/plain Organization: IBM Corporation Date: Thu, 31 Jul 2008 11:10:04 +0200 Message-Id: <1217495404.8555.20.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1247 Lines: 33 On Wed, 2008-07-30 at 15:04 -0700, Greg KH wrote: > On Thu, Jul 31, 2008 at 12:02:04AM +0200, Kay Sievers wrote: > > On Wed, Jul 30, 2008 at 18:56, Martin Schwidefsky > > wrote: > > > > > +#define kmsg_dev_alert(id, dev, format, arg...) \ > > > + printk(__KMSG_CHECK(ALERT, id) KMSG_COMPONENT \ > > > + ": %s: " format, (dev)->bus_id , ## arg) > > > > Care to use dev_name(), bus_id will be removed soon. > > Hm, just use dev_printk() instead, it handles all of these kinds of > changes automatically. Using dev_printk won't work because of the order of the elements of the printk. The kmsg tag should not have a "random" position in the printk but should be the first element. If we use dev_printk the kmsg tag will be the third element, for other kmsg printks it will be the first. In addition the kmsg message tag for the device drivers already includes the driver name .. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin. -- 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/