From: Rusty Russell <rusty@rustcorp.com.au>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org,
large-discuss@lists.sourceforge.net,
Heiko Carstens <Heiko.Carstens@de.ibm.com>,
Jason McMullan <jmcmullan@linuxcare.com>,
Anton Blanchard <antonb@au1.ibm.com>,
Greg Kroah-Hartman <ghartman@us.ibm.com>
Subject: Re: [ANNOUNCE] HotPlug CPU patch against 2.5.0
Date: Thu, 17 Jan 2002 18:28:14 +1100 [thread overview]
Message-ID: <E16R6y7-00079N-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "Wed, 16 Jan 2002 18:21:42 -0800." <Pine.LNX.4.33L2.0201161815580.13155-100000@dragon.pdx.osdl.net>
In message <Pine.LNX.4.33L2.0201161815580.13155-100000@dragon.pdx.osdl.net> you
write:
> Hi-
>
> I've identified and fixed the problems on x86.
> There were problems in arch/i386/kernel/mtrr.c and bluesmoke.c.
>
> In both cases, the problems are with __init functions
> and/or __initdata.
>
> Patch is at end of email. CPU online/offline support now works
> with mtrr.c and bluesmoke.c in my testing.
Hi,
I've put it on my kernel page, and will upload to sf.net in a
little bit.
Thanks!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-01-17 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33L2.0112181748040.20824-100000@dragon.pdx.osdl.net>
2001-12-13 21:29 ` Kimio Suganuma
2001-12-13 22:44 ` Russell King
2001-12-14 0:20 ` Kimio Suganuma
2001-12-14 1:36 ` Dave Jones
2001-12-18 0:21 ` Pavel Machek
2001-12-20 0:17 ` Kimio Suganuma
2002-01-17 2:21 ` Randy.Dunlap
2002-01-17 7:28 ` Rusty Russell [this message]
2001-12-21 21:08 Grover, Andrew
2001-12-22 16:05 ` Pavel Machek
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=E16R6y7-00079N-00@wagner.rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=Heiko.Carstens@de.ibm.com \
--cc=antonb@au1.ibm.com \
--cc=ghartman@us.ibm.com \
--cc=jmcmullan@linuxcare.com \
--cc=large-discuss@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®