public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Mike Travis <travis@sgi.com>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Roland Dreier <rdreier@cisco.com>,
	Randy Dunlap <rdunlap@xenotime.net>, Tejun Heo <tj@kernel.org>,
	Andi Kleen <andi@firstfloor.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	David Rientjes <rientjes@google.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	Jack Steiner <steiner@sgi.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] x86: Limit the number of processor bootup messages
Date: Tue, 17 Nov 2009 12:29:13 -0800	[thread overview]
Message-ID: <4B030799.9020402@zytor.com> (raw)
In-Reply-To: <86802c440911171210x4780c08cg3b3260afd5d2bc5d@mail.gmail.com>

On 11/17/2009 12:10 PM, Yinghai Lu wrote:
>>
>> The following lines have been removed:
>>
>>        CPU: Physical Processor ID:
>>        CPU: Processor Core ID:
>>        CPU %d/0x%x -> Node %d
> 
> please don't.
> 

Why not?

Or, more formally: please state the rationale for keeping them.
	
	-hpa


  reply	other threads:[~2009-11-17 20:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 19:17 [PATCH 0/5] Limit console output by suppressing repetitious messages Mike Travis
2009-11-17 19:17 ` [PATCH 1/5] x86: Limit the number of processor bootup messages Mike Travis
2009-11-17 20:10   ` Yinghai Lu
2009-11-17 20:29     ` H. Peter Anvin [this message]
2009-11-17 21:11       ` Yinghai Lu
2009-11-18  2:38         ` Yinghai Lu
2009-11-18 17:44           ` Mike Travis
2009-11-18 17:43         ` Mike Travis
2009-11-17 21:05     ` Mike Travis
2009-11-18 10:48   ` Borislav Petkov
2009-11-18 17:18     ` Mike Travis
2009-11-18 18:08       ` Borislav Petkov
2009-11-17 19:17 ` [PATCH 2/5] INIT: Limit the number of per cpu calibration " Mike Travis
2009-11-17 19:17 ` [PATCH 3/5] firmware: Limit the number of per cpu firmware messages during bootup Mike Travis
2009-11-17 19:17 ` [PATCH 4/5] sched: Limit the number of scheduler debug messages Mike Travis
2009-11-17 19:17 ` [PATCH 5/5] x86: Limit number of per cpu TSC sync messages Mike Travis
  -- strict thread matches above, loose matches on Subject: below --
2009-11-18  0:22 [PATCH 0/5] Limit console output by suppressing repetitious messages Mike Travis
2009-11-18  0:22 ` [PATCH 1/5] x86: Limit the number of processor bootup messages Mike Travis
2009-11-18  2:45   ` Yinghai Lu
2009-11-18 17:43     ` Mike Travis
2009-11-26  9: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=4B030799.9020402@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=fweisbec@gmail.com \
    --cc=gregkh@suse.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdreier@cisco.com \
    --cc=rdunlap@xenotime.net \
    --cc=rientjes@google.com \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=steiner@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=travis@sgi.com \
    --cc=x86@kernel.org \
    --cc=yhlu.kernel@gmail.com \
    /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