[Patch v4 00/12] memory-hotplug: hot-remove physical memory
Rafael J. Wysocki
rjw at sisk.pl
Wed Nov 28 06:38:00 EST 2012
On Tuesday, November 27, 2012 11:27:41 AM Andrew Morton wrote:
> On Tue, 27 Nov 2012 18:00:10 +0800
> Wen Congyang <wency at cn.fujitsu.com> wrote:
> > The patch-set was divided from following thread's patch-set.
> > https://lkml.org/lkml/2012/9/5/201
> > The last version of this patchset:
> > https://lkml.org/lkml/2012/11/1/93
> As we're now at -rc7 I'd prefer to take a look at all of this after the
> 3.7 release - please resend everything shortly after 3.8-rc1.
> > If you want to know the reason, please read following thread.
> > https://lkml.org/lkml/2012/10/2/83
> Please include the rationale within each version of the patchset rather
> than by linking to an old email. Because
> a) this way, more people are likely to read it
> b) it permits the text to be maimtained as the code evolves
> c) it permits the text to be included in the mainlnie commit, where
> people can find it.
> > The patch-set has only the function of kernel core side for physical
> > memory hot remove. So if you use the patch, please apply following
> > patches.
> > - bug fix for memory hot remove
> > https://lkml.org/lkml/2012/10/31/269
> > - acpi framework
> > https://lkml.org/lkml/2012/10/26/175
> What's happening with the acpi framework? has it received any feedback
> from the ACPI developers?
This particular series is in my tree waiting for the v3.8 merge window.
There's a new one sent yesterday and this one is pending a review. I'm
not sure if the $subject patchset depends on it, though.
It looks like there are too many hotplug patchsets flying left and right and
it's getting hard to keep track of them all.
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
More information about the Linuxppc-dev