From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Yasunori Goto <y-goto@jp.fujitsu.com>,
Christoph Lameter <clameter@sgi.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0 of 4] [RFC] hotplug memory: minor updates
Date: Fri, 28 Mar 2008 09:07:11 -0700 [thread overview]
Message-ID: <47ED17AF.5030804@goop.org> (raw)
In-Reply-To: <20080328091250.GH21413@elte.hu>
Ingo Molnar wrote:
> the x86 bits look small and trivial, so i'd suggest you get this into
> -mm to after all the other VM patches, because this seems primarily a VM
> issue.
>
I would do that, but I'm planning on posting some Xen balloon driver
patches which depend on at least one of these patches.
I'll drop "hotplug-memory: adding non-section-aligned memory is bad"
because it was just warnings and it was NACKed. "hotplug-memory: add
add_memory_resource()" is just a refactor, and should be a noop as far
as the existing add_memory() is concerned.
> i've applied #3 to x86.git straight away. Does #4 have dependencies on
> the other patches? I suspect it does so it cannot be applied standalone.
>
You mean the "paravirt_ops: don't steal memory resources in
paravirt_disable_iospace"? That shouldn't have any dependencies. It's
the only patch in my queue which even references that file. Rusty said
he picked it up too; are you exchanging patches with him?
J
next prev parent reply other threads:[~2008-03-28 16:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 0:28 [PATCH 0 of 4] [RFC] hotplug memory: minor updates Jeremy Fitzhardinge
2008-03-28 0:28 ` [PATCH 1 of 4] hotplug-memory: add add_memory_resource Jeremy Fitzhardinge
2008-03-28 0:28 ` [PATCH 2 of 4] hotplug-memory: adding non-section-aligned memory is bad Jeremy Fitzhardinge
2008-03-28 1:27 ` KAMEZAWA Hiroyuki
2008-03-28 1:34 ` Yasunori Goto
2008-03-28 1:54 ` KAMEZAWA Hiroyuki
2008-03-28 2:13 ` Jeremy Fitzhardinge
2008-03-28 2:33 ` KAMEZAWA Hiroyuki
2008-03-28 2:51 ` Jeremy Fitzhardinge
2008-03-28 3:17 ` KAMEZAWA Hiroyuki
2008-03-28 4:20 ` Jeremy Fitzhardinge
2008-03-28 4:39 ` KAMEZAWA Hiroyuki
2008-03-28 18:19 ` Jeremy Fitzhardinge
2008-03-28 18:27 ` Dave Hansen
2008-03-28 3:21 ` Yasunori Goto
2008-03-28 4:07 ` Jeremy Fitzhardinge
2008-03-28 21:30 ` Jeremy Fitzhardinge
2008-03-28 0:28 ` [PATCH 3 of 4] sparsemem: reduce i386 PAE section size Jeremy Fitzhardinge
2008-03-28 0:35 ` Christoph Lameter
2008-03-28 2:26 ` Jeremy Fitzhardinge
2008-03-28 2:27 ` Christoph Lameter
2008-03-28 6:18 ` Jeremy Fitzhardinge
2008-03-28 16:43 ` Dave Hansen
2008-03-28 18:05 ` Jeremy Fitzhardinge
2008-03-28 16:45 ` Dave Hansen
2008-03-28 0:28 ` [PATCH 4 of 4] paravirt_ops: don't steal memory resources in paravirt_disable_iospace Jeremy Fitzhardinge
2008-03-28 2:41 ` Rusty Russell
2008-03-28 9:12 ` [PATCH 0 of 4] [RFC] hotplug memory: minor updates Ingo Molnar
2008-03-28 16:07 ` Jeremy Fitzhardinge [this message]
2008-03-28 22:04 ` Ingo Molnar
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=47ED17AF.5030804@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=dave@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=y-goto@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox