From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: "Brown, Len" <len.brown@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Subject: Re: [PATCH] Add memory hotadd to pvops dom0
Date: Tue, 22 Dec 2009 12:54:49 -0800 [thread overview]
Message-ID: <4B313219.6030803@goop.org> (raw)
In-Reply-To: <C8EDE645B81E5141A8C6B2F73FD9265107A292F9FA@shzsmsx501.ccr.corp.intel.com>
On 12/22/2009 03:29 AM, Jiang, Yunhong wrote:
> Re-submit based on Konrad's feedback.
>
> BTW, Jeremy, I'm not sure if we can keep the changes to drivers/acpi/acpi_memhotplug.c as internal changes, if it is un-acceptable by upstream? I remember in Xen summit, it is said acceptable to keep small xen-specific changes.
>
> In fact, I'm not sure if any changes to acpi stuff can be in upstream kernel, although Ke has take a lot of effort to make it cleaner.
>
Yes, I'm concerned about that too. It would be useful to put together a
clean set of all our ACPI changes against upstream to see how it looks
afresh, and see to what extent Len can bring himself to like them.
J
next prev parent reply other threads:[~2009-12-22 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 11:29 [PATCH] Add memory hotadd to pvops dom0 Jiang, Yunhong
2009-12-22 20:54 ` Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-18 10:27 Jiang, Yunhong
2009-12-18 14:19 ` Konrad Rzeszutek Wilk
2009-12-19 14:47 ` Jiang, Yunhong
2009-12-20 6:40 ` Jeremy Fitzhardinge
2009-12-20 8:04 ` Keir Fraser
2009-12-20 16:04 ` Jeremy Fitzhardinge
2009-12-19 0:06 ` Jeremy Fitzhardinge
2009-12-19 14:04 ` Jiang, Yunhong
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=4B313219.6030803@goop.org \
--to=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.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.