The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Andi Kleen <ak@suse.de>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: introduce initial apicid
Date: Fri, 7 Mar 2008 12:02:06 +0100	[thread overview]
Message-ID: <20080307110206.GI9021@bingen.suse.de> (raw)
In-Reply-To: <86802c440803061346u350d395djacf5e1aefffb0e4b@mail.gmail.com>

On Thu, Mar 06, 2008 at 01:46:39PM -0800, Yinghai Lu wrote:
> 

> [PATCH] x86: introduce initial apicid
> 
> store initial_apicid from early identify. it is could be different from phys_proc_id later
> 
> also print it out in proc

Looks good to me now.

-Andi

      parent reply	other threads:[~2008-03-07 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 21:46 [PATCH] x86: introduce initial apicid Yinghai Lu
2008-03-07  8:47 ` Ingo Molnar
2008-03-07 11:02 ` Andi Kleen [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=20080307110206.GI9021@bingen.suse.de \
    --to=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --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