mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Joe Perches <joe@perches.com>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	jbeulich@novell.com, tglx@linutronix.de,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/debug] x86: Combine printk()s in show_regs_common()
Date: Fri, 18 Feb 2011 22:15:51 +0100	[thread overview]
Message-ID: <20110218211551.GA7494@elte.hu> (raw)
In-Reply-To: <1298060386.15565.25.camel@Joe-Laptop>


* Joe Perches <joe@perches.com> wrote:

> On Fri, 2011-02-18 at 21:05 +0100, Ingo Molnar wrote:
> > * Joe Perches <joe@perches.com> wrote:
> > > Ingo, why did you choose to apply this patch instead of
> > > the alternative one I posted on the same thread?
> > Your version:
> > 
> > 	/* Board Name is optional */
> > 	board = dmi_get_system_info(DMI_BOARD_NAME);
> > 	if (!board)
> > 		board = "";
> > 
> > 	printk(KERN_CONT "\n");
> > 
> > 	printk(KERN_DEFAULT "Pid: %d, comm: %.20s %s %s %.*s %s %s%s%s\n",
> > 	       current->pid, current->comm, print_tainted(),
> > 	       init_utsname()->release,
> > 	       (int)strcspn(init_utsname()->version, " "),
> > 	       init_utsname()->version,
> > 	       vendor, product,
> > 	       strlen(board) ? "/" : "",
> > 	       board);
> > 
> > The 'board' fiddling and the strlen(board) check complicates things unnecessarily 
> > and makes the code hard to read. Jan's version was at least simple.
> 
> Perhaps you should look at the surrounding code.
> It's uses the same style as I chose for "board".

Yes, i realize that, but the strlen() trick really looks weird.

And 'weird' is not something i like seeing in essential bug reporting code.

Thanks,

	Ingo

      reply	other threads:[~2011-02-18 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 15:56 [PATCH] x86: combine " Jan Beulich
2011-02-17 18:53 ` Joe Perches
2011-02-18 10:40 ` [tip:x86/debug] x86: Combine " tip-bot for Jan Beulich
2011-02-18 19:41   ` Joe Perches
2011-02-18 20:05     ` Ingo Molnar
2011-02-18 20:19       ` Joe Perches
2011-02-18 21:15         ` Ingo Molnar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110218211551.GA7494@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=jbeulich@novell.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome