From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: David Rientjes <rientjes@google.com>,
Wen Congyang <wency@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-acpi@vger.kernel.org, Len Brown <len.brown@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Jiang Liu <jiang.liu@huawei.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>, Mel Gorman <mgorman@suse.de>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Toshi Kani <toshi.kani@hp.com>
Subject: Re: [Patch v5 0/7] acpi,memory-hotplug: implement framework for hot removing memory
Date: Fri, 16 Nov 2012 00:33:17 +0100 [thread overview]
Message-ID: <5603900.8uSmar4juL@vostro.rjw.lan> (raw)
In-Reply-To: <1637174.XPDXHMEQY8@vostro.rjw.lan>
On Friday, November 16, 2012 12:22:58 AM Rafael J. Wysocki wrote:
> On Thursday, November 15, 2012 02:51:52 PM David Rientjes wrote:
> > On Thu, 15 Nov 2012, Wen Congyang wrote:
> >
> > > Note:
> > > 1. The following commit in pm tree can be dropped now(The other two patches
> > > are already dropped):
> > > 54c4c7db6cb94d7d1217df6d7fca6847c61744ab
> > > 2. This patchset requires the following patch(It is in pm tree now)
> > > https://lkml.org/lkml/2012/11/1/225
> > >
> >
> > So this is based on the acpi-general branch of
> > git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git correct?
>
> It should be based on that, yes.
>
> > And the branch's HEAD commit 54c4c7db6cb9 ("ACPI / memory-hotplug: call
> > acpi_bus_trim() to remove memory device") can be reverted before this
> > series is applied?
>
> Why?
Ah, because of patch [2/7]. I wonder what tree this one is supposed to
apply to. Surely not to linux-pm.git/acpi-general.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-11-15 23:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 6:59 Wen Congyang
2012-11-15 6:59 ` [Patch v5 1/7] acpi,memory-hotplug : add memory offline code to acpi_memory_device_remove() Wen Congyang
2012-11-15 23:03 ` David Rientjes
2012-11-15 6:59 ` [Patch v5 2/7] acpi,memory-hotplug: deal with eject request in hotplug queue Wen Congyang
2012-11-15 9:13 ` Yasuaki Ishimatsu
2012-11-15 22:09 ` Toshi Kani
2012-11-15 23:32 ` David Rientjes
2012-11-16 1:54 ` Wen Congyang
2012-11-15 6:59 ` [Patch v5 3/7] acpi_memhotplug.c: fix memory leak when memory device is unbound from the module acpi_memhotplug Wen Congyang
2012-11-15 9:15 ` Yasuaki Ishimatsu
2012-11-15 23:34 ` David Rientjes
2012-11-15 6:59 ` [Patch v5 4/7] acpi_memhotplug.c: free memory device if acpi_memory_enable_device() failed Wen Congyang
2012-11-15 9:17 ` Yasuaki Ishimatsu
2012-11-15 23:36 ` David Rientjes
2012-11-15 6:59 ` [Patch v5 5/7] acpi_memhotplug.c: don't allow to eject the memory device if it is being used Wen Congyang
2012-11-15 9:20 ` Yasuaki Ishimatsu
2012-11-15 23:39 ` David Rientjes
2012-11-29 13:15 ` andywu106建国
2012-11-15 6:59 ` [Patch v5 6/7] acpi_memhotplug.c: bind the memory device when the driver is being loaded Wen Congyang
2012-11-15 9:22 ` Yasuaki Ishimatsu
2012-11-15 23:40 ` David Rientjes
2012-11-15 6:59 ` [Patch v5 7/7] acpi_memhotplug.c: auto bind the memory device which is hotplugged before the driver is loaded Wen Congyang
2012-11-15 9:57 ` Yasuaki Ishimatsu
2012-11-15 22:45 ` Toshi Kani
2012-11-15 22:51 ` [Patch v5 0/7] acpi,memory-hotplug: implement framework for hot removing memory David Rientjes
2012-11-15 23:22 ` Rafael J. Wysocki
2012-11-15 23:33 ` Rafael J. Wysocki [this message]
2012-11-16 0:28 ` Rafael J. Wysocki
2012-11-16 0:40 ` Rafael J. Wysocki
2012-11-16 0:40 ` Toshi Kani
2012-11-16 1:02 ` Rafael J. Wysocki
2012-11-16 1:07 ` Yasuaki Ishimatsu
2012-11-16 1:28 ` Rafael J. Wysocki
2012-11-16 1:31 ` Yasuaki Ishimatsu
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=5603900.8uSmar4juL@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=konrad.wilk@oracle.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=rientjes@google.com \
--cc=toshi.kani@hp.com \
--cc=wency@cn.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