All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jiang, Yunhong" <yunhong.jiang@intel.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: RE: [PATCH] Add cpu hotplug support for 2.6.32 branch
Date: Mon, 23 Aug 2010 11:02:54 +0800	[thread overview]
Message-ID: <789F9655DD1B8F43B48D77C5D306597329D95F5C@shsmsx501.ccr.corp.intel.com> (raw)
In-Reply-To: <4C6F21A7.6000605@goop.org>



>-----Original Message-----
>From: Jeremy Fitzhardinge [mailto:jeremy@goop.org]
>Sent: Saturday, August 21, 2010 8:45 AM
>To: Jiang, Yunhong
>Cc: Xen-devel
>Subject: Re: [Xen-devel] [PATCH] Add cpu hotplug support for 2.6.32 branch
>
> On 08/19/2010 08:45 PM, Jiang, Yunhong wrote:
>> Jeremy, I think all this patch is purely for acpi changes, so not sure if it is ok to apply
>it on origin/xen/dom0/acpi-next?
>> I have a talk with Ke, the xen/dom0/acpi-next has already covere all work for PM
>and CPU/Mem hotplug in a cleaner way and is based on 2.6.32 kernel, so maybe we
>can use that for the base tree.
>
>I'm not sure what you mean by the "base tree".  As far as I know,
>everything is already merged into the 2.6.32 tree.  Have I overlooked
>something?

Sorry, it's not you overlook, but we. We didn't port the CPU hotplug patch to 2.6.32 kernel.

Thanks
--jyh

>
>Thanks,
>    J

      reply	other threads:[~2010-08-23  3:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  3:04 [PATCH] Add cpu hotplug support for 2.6.32 branch Jiang, Yunhong
2010-08-18  9:54 ` Jan Beulich
2010-08-19  5:02   ` Jiang, Yunhong
2010-08-18 19:41 ` Jeremy Fitzhardinge
2010-08-20  3:45   ` Jiang, Yunhong
2010-08-21  0:45     ` Jeremy Fitzhardinge
2010-08-23  3:02       ` Jiang, Yunhong [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=789F9655DD1B8F43B48D77C5D306597329D95F5C@shsmsx501.ccr.corp.intel.com \
    --to=yunhong.jiang@intel.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.