From: Ashok Raj <ashok.raj@intel.com>
To: Andi Kleen <ak@muc.de>
Cc: Ashok Raj <ashok.raj@intel.com>,
zwane@arm.linux.org.uk, discuss@x86-64.org, shaohua.li@intel.com,
linux-kernel@vger.kernel.org, rusty@rustycorp.com.au,
vatsa@in.ibm.com
Subject: Re: [patch 2/4] CPU hot-plug support for x86_64
Date: Mon, 23 May 2005 10:32:12 -0700 [thread overview]
Message-ID: <20050523103211.A8692@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050523172424.GG39821@muc.de>; from ak@muc.de on Mon, May 23, 2005 at 07:24:24PM +0200
On Mon, May 23, 2005 at 07:24:24PM +0200, Andi Kleen wrote:
> On Mon, May 23, 2005 at 09:58:17AM -0700, Ashok Raj wrote:
> >
> > If its for documentation, then its ok, the reason i thought it will
> > be dead code/documentation soon is since 90% of the hotplug code is
> > generic kernel code, which is not under __cpuinit, just some pieces of
> > x86_64 would alone exist this way, and will not serve real purpose very soon.
>
> I would hope these other pieces get converted over. I will probably
> look into that soon if nobody beats me.
>
If my IRC, this is how we got started early days. I remember rusty changed them
during the end of the real development.
Rusty/Vatsa would know the exact scope on why we went away from __cpuinit.
[Both who's names i missed accidently in ccing, when i was trying the new
quilt mail, i exited by mistake, and it sent to the partial list, sorry guys]
--
Cheers,
Ashok Raj
- Open Source Technology Center
next prev parent reply other threads:[~2005-05-23 17:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 22:16 [patch 0/4] CPU hot-plug support for x86_64 Ashok Raj
2005-05-20 22:16 ` [patch 1/4] " Ashok Raj
2005-05-20 22:16 ` [patch 2/4] " Ashok Raj
2005-05-23 16:38 ` Andi Kleen
2005-05-23 16:58 ` Ashok Raj
2005-05-23 17:24 ` Andi Kleen
2005-05-23 17:32 ` Ashok Raj [this message]
2005-05-23 19:37 ` Rafael J. Wysocki
2005-05-24 11:49 ` Andi Kleen
2005-05-20 22:16 ` [patch 3/4] " Ashok Raj
2005-05-20 22:16 ` [patch 4/4] " Ashok Raj
2005-05-23 16:40 ` [patch 0/4] " Andi Kleen
2005-05-23 16:54 ` Ashok Raj
2005-05-23 17:12 ` Andi Kleen
2005-05-23 17:40 ` [discuss] " Ashok Raj
2005-05-24 5:46 ` Srivatsa Vaddagiri
2005-05-24 6:01 ` Ashok Raj
2005-05-24 8:53 ` Srivatsa Vaddagiri
2005-05-24 18:17 ` Andi Kleen
2005-05-24 11:50 ` Andi Kleen
2005-05-24 11:48 ` Andi Kleen
2005-05-24 17:01 ` Srivatsa Vaddagiri
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=20050523103211.A8692@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=ak@muc.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustycorp.com.au \
--cc=shaohua.li@intel.com \
--cc=vatsa@in.ibm.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