From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
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: Tue, 21 Jan 2020 15:18:23 +0000 [thread overview]
Message-ID: <20200121151822.GA13306@willie-the-truck> (raw)
In-Reply-To: <1579157135-10360-1-git-send-email-anshuman.khandual@arm.com>
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.
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().
So I think I'll leave this for 5.7.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: mark.rutland@arm.com, david@redhat.com, catalin.marinas@arm.com,
linux-mm@kvack.org, arunks@codeaurora.org,
cpandya@codeaurora.org, ira.weiny@intel.com, logang@deltatee.com,
steven.price@arm.com, valentin.schneider@arm.com,
suzuki.poulose@arm.com, broonie@kernel.org, cai@lca.pw,
ard.biesheuvel@arm.com, dan.j.williams@intel.com,
linux-arm-kernel@lists.infradead.org, osalvador@suse.de,
steve.capper@arm.com, Robin.Murphy@arm.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mgorman@techsingularity.net
Subject: Re: [PATCH V12 0/2] arm64/mm: Enable memory hot remove
Date: Tue, 21 Jan 2020 15:18:23 +0000 [thread overview]
Message-ID: <20200121151822.GA13306@willie-the-truck> (raw)
In-Reply-To: <1579157135-10360-1-git-send-email-anshuman.khandual@arm.com>
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.
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().
So I think I'll leave this for 5.7.
Will
_______________________________________________
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:[~2020-01-21 15:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 6:45 [PATCH V12 0/2] arm64/mm: Enable memory hot remove Anshuman Khandual
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-16 6:45 ` Anshuman Khandual
2020-01-21 12:02 ` Catalin Marinas
2020-01-21 12:02 ` Catalin Marinas
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-16 6:45 ` Anshuman Khandual
2020-01-21 12:02 ` Catalin Marinas
2020-01-21 12:02 ` Catalin Marinas
2020-01-21 12:02 ` Catalin Marinas
2020-01-21 15:18 ` Will Deacon [this message]
2020-01-21 15:18 ` [PATCH V12 0/2] " Will Deacon
2020-01-22 3:35 ` Anshuman Khandual
2020-01-22 3:35 ` Anshuman Khandual
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=20200121151822.GA13306@willie-the-truck \
--to=will@kernel.org \
--cc=Robin.Murphy@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.