From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Reinecke Subject: Re: [RFC PATCH 0/4] Persistent device name using alias name Date: Mon, 11 Jul 2011 13:47:24 +0200 Message-ID: <4E1AE2CC.4010501@suse.de> References: <20110708084547.2091.55262.stgit@ltc197.sdl.hitachi.co.jp> <20110708145408.GA2283@kroah.com> <20110708154736.GA7320@kroah.com> <1310140451.3282.85.camel@mulgrave> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Kay Sievers Cc: James Bottomley , Greg KH , Nao Nishijima , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, jcm@redhat.com, dle-develop@lists.sourceforge.net, Masami Hiramatsu , yrl.pp-manager.tt@hitachi.com, dgilbert@interlog.com, stefanr@s5r6.in-berlin.de List-Id: linux-scsi@vger.kernel.org On 07/08/2011 06:38 PM, Kay Sievers wrote: > On Fri, Jul 8, 2011 at 18:15, Kay Sievers wrot= e: >> On Fri, Jul 8, 2011 at 17:54, James Bottomley > >>> But hey, >>> you have the enthusiasm, propose it as a KS topic to get agreement = that >>> we should do it and what the format should be and we can go from th= ere. >> >> Sure, I'll do that. If needed, I can even make half or a third of it >> possible I guess. > > Submitted it a minute ago. > I'd be willing to working on the design here, as it ties in rather=20 neatly with my goal of updating the SCSI debugging facilities. printk() is easy to write, but basically impossible to impose any=20 type of checking/format whatever. My all-time favorite here: printk(KERN_INFO "error 1\n"); At least it got a 'KERN_INFO' thrown in there ... So first step would be to reach an agreement _what_ printk() et al=20 is supposed to convey to userland. Informal only? Informal, but traceable to the origin? Should the origin be the internal=20 structure/subsystem/device/whatever generating the error? Should the origin be persistent across reboots? And, tied to that, what the supposed audience for printk() is: Programs? Syslog? Humans? Once we have an agreement here we can then go about and code the=20 required pieces. But currently the main problem is that there are=20 different ideas of what printk() is supposed to do. Cheers, Hannes --=20 Dr. Hannes Reinecke zSeries & Storage hare@suse.de +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg GF: J. Hawn, J. Guild, F. Imend=C3=B6rffer, HRB 16746 (AG N=C3=BCrnberg= )