From: Andi Kleen <ak@suse.de>
To: James Cleverdon <jamesclv@us.ibm.com>
Cc: Chris Wright <chrisw@osdl.org>, ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clustered apic patch missing APIC_DFR_CLUSTER def
Date: Fri, 29 Oct 2004 01:38:05 +0200 [thread overview]
Message-ID: <20041028233805.GA11384@wotan.suse.de> (raw)
In-Reply-To: <200410281635.23848.jamesclv@us.ibm.com>
On Thu, Oct 28, 2004 at 04:35:23PM -0700, James Cleverdon wrote:
> Hmmm... The patch containing APIC_DFR_CLUSTER and friends went
> into the -mm tree in the June/July timeframe. It must not have
> been pushed with the main cluster patch.
Andrew moved it into the x86-64 kexec APIC patch for some unknown
reason. And that obviously was not pushed ...
I already sent a patch to Linus and will send patches for
the other known buglets too (warnings, safe_smp_processor_id())
-Andi
next prev parent reply other threads:[~2004-10-28 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 18:27 [PATCH] clustered apic patch missing APIC_DFR_CLUSTER def Chris Wright
2004-10-28 23:35 ` James Cleverdon
2004-10-28 23:38 ` Andi Kleen [this message]
2004-10-28 23:51 ` Chris Wright
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=20041028233805.GA11384@wotan.suse.de \
--to=ak@suse.de \
--cc=chrisw@osdl.org \
--cc=jamesclv@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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