From: Will Deacon <will.deacon@arm.com>
To: Maciej Bielski <m.bielski@virtualopensystems.com>
Cc: Scott Branden <scott.branden@broadcom.com>,
Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Xishi Qiu <qiuxishi@huawei.com>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Tang Chen <tangchen@cn.fujitsu.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Andrea Reale2 <REALEAN2@ie.ibm.com>,
Kostas Katrinis <katrinisk@ie.ibm.com>,
Christian Pinto <c.pinto@virtualopensystems.com>
Subject: Re: [RFC PATCH 0/2] arm64: memory-hotplug: Add Memory Hotplug support
Date: Fri, 2 Dec 2016 10:49:07 +0000 [thread overview]
Message-ID: <20161202104907.GB8266@arm.com> (raw)
In-Reply-To: <18021c70-a4a0-3007-c861-82ede74f965e@virtualopensystems.com>
On Fri, Dec 02, 2016 at 10:13:43AM +0100, Maciej Bielski wrote:
> Recently we have announced our effort on that:
> https://lkml.org/lkml/2016/11/17/49
>
> For now we have a working solution for hotplug and we are performing
> code cleanup to push the patches soon.
Are these intended to replace or extend Scott's patches? If the former,
please work with Scott's stuff as a base rather than posting a competing
series.
Will
next prev parent reply other threads:[~2016-12-02 10:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 0:19 Scott Branden
2016-12-02 0:19 ` [RFC PATCH 1/2] arm64: memory-hotplug: Add MEMORY_HOTPLUG, MEMORY_HOTREMOVE, MEMORY_PROBE Scott Branden
2016-12-02 0:19 ` [RFC PATCH 2/2] arm64: defconfig: enable MEMORY_HOTPLUG config options Scott Branden
2016-12-02 1:49 ` [RFC PATCH 0/2] arm64: memory-hotplug: Add Memory Hotplug support Xishi Qiu
2016-12-02 2:38 ` Scott Branden
2016-12-02 3:11 ` Xishi Qiu
2016-12-07 8:43 ` Scott Branden
2016-12-07 11:21 ` Xishi Qiu
2016-12-02 9:13 ` Maciej Bielski
2016-12-02 10:49 ` Will Deacon [this message]
2016-12-02 10:55 ` Maciej Bielski
2016-12-02 17:40 ` Scott Branden
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=20161202104907.GB8266@arm.com \
--to=will.deacon@arm.com \
--cc=REALEAN2@ie.ibm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=c.pinto@virtualopensystems.com \
--cc=catalin.marinas@arm.com \
--cc=katrinisk@ie.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.bielski@virtualopensystems.com \
--cc=mark.rutland@arm.com \
--cc=qiuxishi@huawei.com \
--cc=scott.branden@broadcom.com \
--cc=tangchen@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
Powered by JetHome