From: Andi Kleen <ak@suse.de>
To: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: Andi Kleen <ak@suse.de>,
akpm@osdl.org, zwane@arm.linux.org.uk, len.brown@intel.com,
venkatesh.pallipadi@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/1] Do not enforce unique IO_APIC_ID for Xeon processors in EM64T mode (x86_64)
Date: Mon, 9 May 2005 01:53:29 +0200 [thread overview]
Message-ID: <20050508235329.GA27717@wotan.suse.de> (raw)
In-Reply-To: <19D0D50E9B1D0A40A9F0323DBFA04ACCE04B51@USRV-EXCH4.na.uis.unisys.com>
On Sun, May 08, 2005 at 12:28:26PM -0500, Protasevich, Natalie wrote:
>
> > > Sure, I will remove the io_apic_get_unique_id() then.
> > Perhaps, it will
> > > be easy to put it back in if someone implements a chipset
> > that needs it.
> >
> > I did it myself now.
> >
>
> Ok, great, I was about to put it together, but you beat me to it :) You
> probably don't need the "#define IO_APIC_MAX_ID 0xFE: line
> anymore?
Removed now, thanks.
-Andi
next prev parent reply other threads:[~2005-05-08 23:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 17:28 Protasevich, Natalie
2005-05-08 23:53 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-12 2:22 Protasevich, Natalie
2005-05-11 16:21 Protasevich, Natalie
2005-05-11 19:22 ` Andi Kleen
2005-05-11 7:10 Protasevich, Natalie
2005-05-11 11:22 ` Andi Kleen
2005-05-08 5:01 Protasevich, Natalie
2005-05-08 13:49 ` Andi Kleen
2005-05-09 19:15 ` James Cleverdon
2005-05-07 5:34 Natalie.Protasevich
2005-05-08 1:00 ` Zwane Mwaikambo
2005-05-05 22:11 Natalie.Protasevich
2005-05-06 17:34 ` Len Brown
2005-05-06 17:57 ` Zwane Mwaikambo
2005-05-07 13:41 ` Andi Kleen
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=20050508235329.GA27717@wotan.suse.de \
--to=ak@suse.de \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
--cc=zwane@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®