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

On Fri, 2011-02-18 at 10:40 +0000, tip-bot for Jan Beulich wrote:
> Commit-ID:  fd8fa4d3ddc4cc04ec8097e632b995d535c52beb
> Gitweb:     http://git.kernel.org/tip/fd8fa4d3ddc4cc04ec8097e632b995d535c52beb
> Author:     Jan Beulich <JBeulich@novell.com>
> AuthorDate: Thu, 17 Feb 2011 15:56:58 +0000
> Committer:  Ingo Molnar <mingo@elte.hu>
> CommitDate: Fri, 18 Feb 2011 08:52:30 +0100
> 
> x86: Combine printk()s in show_regs_common()
> 
> Printing a single character alone when there's an immediately
> following printk() is pretty pointless (and wasteful).

Ingo, why did you choose to apply this patch instead of
the alternative one I posted on the same thread?

https://patchwork.kernel.org/patch/571641/



  reply	other threads:[~2011-02-18 19:41 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 [this message]
2011-02-18 20:05     ` Ingo Molnar
2011-02-18 20:19       ` Joe Perches
2011-02-18 21:15         ` Ingo Molnar

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=1298058105.15565.4.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=hpa@zytor.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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