From: Catalin Marinas <catalin.marinas@arm.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: will@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] arm64: defconfig: Enable memory hotplug and hotremove config
Date: Thu, 1 Sep 2022 11:38:59 +0100 [thread overview]
Message-ID: <YxCLw5P8u1YnyIbV@arm.com> (raw)
In-Reply-To: <16d83454-341c-8839-25b6-2094e7a35478@huawei.com>
On Thu, Aug 25, 2022 at 09:09:17PM +0800, Kefeng Wang wrote:
> On 2022/6/30 18:53, Catalin Marinas wrote:
> > On Thu, Jun 30, 2022 at 09:26:17AM +0800, Kefeng Wang wrote:
> > > On 2022/6/29 17:35, Kefeng Wang wrote:
> > > > Let's enable ACPI_HMAT, ACPI_HOTPLUG_MEMORY, MEMORY_HOTPLUG
> > > > and MEMORY_HOTREMOVE for more test coverage, also there are
> > > > useful for heterogeneous memory scene.
> > > Hi Catalin and Will，is the defconfig patch picked up from you directly，
> > > the changelog shows most of them merged by SoC maintainers, but this
> > > one is some general feature, I don't know who will take it, thanks.
> > In general we leave the defconfig patches to the SoC team to avoid
> > conflicts as they have a lot more changes. Cc'ing Arnd if he wants to
> > pick it up, otherwise it can go through the arm64 tree.
> >
> > Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
>
> Hi maintainers, look this patch is missed, could anyone pick it up,
I added it to my list of patches for 6.1. I'll queue it around rc6
unless Arnd takes it before (and of course, if it won't conflict to the
other SoC changes to defconfig).
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-01 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 9:35 [PATCH v2] arm64: defconfig: Enable memory hotplug and hotremove config Kefeng Wang
2022-06-30 1:26 ` Kefeng Wang
2022-06-30 10:53 ` Catalin Marinas
2022-07-12 14:24 ` Kefeng Wang
2022-08-25 13:09 ` Kefeng Wang
2022-09-01 10:38 ` Catalin Marinas [this message]
2022-09-01 13:12 ` Kefeng Wang
2022-06-30 7:10 ` Anshuman Khandual
2022-06-30 10:49 ` Catalin Marinas
2022-09-21 12:47 ` Catalin Marinas
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=YxCLw5P8u1YnyIbV@arm.com \
--to=catalin.marinas@arm.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).