From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH 5 of 5] xentrace: use consistent printk prefix Date: Wed, 23 Mar 2011 17:02:40 +0000 Message-ID: <1300899760.2827.33.camel@silas> References: <4D89D6030200007800037DC1@vpn.id2.novell.com> <20110323111832.GA28535@aepfle.de> <1300891647.2827.10.camel@silas> <4D8A2BFA0200007800037F22@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D8A2BFA0200007800037F22@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: Olaf Hering , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Wed, 2011-03-23 at 16:20 +0000, Jan Beulich wrote: > >>> On 23.03.11 at 15:47, George Dunlap wrote: > > I'd prefer something a tiny bit more descriptive, like "xentrace:", but > > I would acquiesce to xtb if someone felt strongly about it. > > I was nagging just because "Xen trace buffers: " seemed overly long > to me. I'm fine with your preference. I agree that "Xen trace buffers" is too long -- debug output on a serial line is somewhat precious when your machine is crashing. :-) Olaf, are you OK with making the prefix consistently "xentrace"? -George > > Jan > > > -George > > > > On Wed, 2011-03-23 at 11:18 +0000, Olaf Hering wrote: > >> On Wed, Mar 23, Jan Beulich wrote: > >> > >> > >>> On 22.03.11 at 20:21, Olaf Hering wrote: > >> > > # HG changeset patch > >> > > # User Olaf Hering > >> > > # Date 1300813820 -3600 > >> > > # Node ID dcbae547cce81f10c243d54bd35fd139615313cb > >> > > # Parent e58f6949e76a2786c4f5a99a0da44ee58743b4df > >> > > xentrace: use consistent printk prefix > >> > > >> > Why "Xen trace buffers: " and not e.g. "xtb: "? > >> > >> Its used in other printk calls already. > >> George, would a change to xtb: be ok for you for all existing printk calls? > >> > >> Olaf > > >