From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, akpm@linux-foundation.org,
catalin.marinas@arm.com, mark.rutland@arm.com, david@redhat.com,
cai@lca.pw, logang@deltatee.com, cpandya@codeaurora.org,
arunks@codeaurora.org, dan.j.williams@intel.com,
mgorman@techsingularity.net, osalvador@suse.de,
ard.biesheuvel@arm.com, steve.capper@arm.com, broonie@kernel.org,
valentin.schneider@arm.com, Robin.Murphy@arm.com,
steven.price@arm.com, suzuki.poulose@arm.com,
ira.weiny@intel.com
Subject: Re: [PATCH V12 0/2] arm64/mm: Enable memory hot remove
Date: Wed, 22 Jan 2020 09:05:03 +0530 [thread overview]
Message-ID: <3cbdc6f9-093d-975e-f960-68c274aa75a1@arm.com> (raw)
In-Reply-To: <20200121151822.GA13306@willie-the-truck>
On 01/21/2020 08:48 PM, Will Deacon wrote:
> On Thu, Jan 16, 2020 at 12:15:33PM +0530, Anshuman Khandual wrote:
>> This series enables memory hot remove functionality on arm64 platform. This
>> is based on Linux 5.5-rc6 and particularly deals with a problem caused when
>> boot memory is attempted to be removed.
Hello Will,
>
> Unfortunately, this results in a conflict with mainline since the arm64
> -next branches are based on -rc3 and there was a fix merged after that
> (feee6b298916 ("mm/memory_hotplug: shrink zones when offlining memory"))
> which changes the type of __remove_pages().
Right, that fix went in last couple of weeks.
>
> So I think I'll leave this for 5.7.
Just wondering if there is any chance this can still make it to 5.6
or its already too late ?
>
> Will
>
- Anshuman
prev parent reply other threads:[~2020-01-22 3:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 6:45 Anshuman Khandual
2020-01-16 6:45 ` [PATCH V12 1/2] arm64/mm: Hold memory hotplug lock while walking for kernel page table dump Anshuman Khandual
2020-01-21 12:02 ` Catalin Marinas
2020-01-16 6:45 ` [PATCH V12 2/2] arm64/mm: Enable memory hot remove Anshuman Khandual
2020-01-21 12:02 ` Catalin Marinas
2020-01-21 15:18 ` [PATCH V12 0/2] " Will Deacon
2020-01-22 3:35 ` Anshuman Khandual [this message]
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=3cbdc6f9-093d-975e-f960-68c274aa75a1@arm.com \
--to=anshuman.khandual@arm.com \
--cc=Robin.Murphy@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@arm.com \
--cc=arunks@codeaurora.org \
--cc=broonie@kernel.org \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=cpandya@codeaurora.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=ira.weiny@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=mark.rutland@arm.com \
--cc=mgorman@techsingularity.net \
--cc=osalvador@suse.de \
--cc=steve.capper@arm.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=valentin.schneider@arm.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