From: Will Deacon <will@kernel.org>
To: akpm@linux-foundation.org, linux-mm@kvack.org,
anshuman.khandual@arm.com, linux-arm-kernel@lists.infradead.org,
logang@deltatee.com, mhocko@suse.com, ardb@kernel.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
rppt@kernel.org, jmorris@namei.org, tyhicks@linux.microsoft.com,
Pavel Tatashin <pasha.tatashin@soleen.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH v3 0/1] correct the inside linear map range during hotplug check
Date: Mon, 22 Mar 2021 13:19:58 +0000 [thread overview]
Message-ID: <161641726115.3901166.7580035330760911434.b4-ty@kernel.org> (raw)
In-Reply-To: <20210216150351.129018-1-pasha.tatashin@soleen.com>
On Tue, 16 Feb 2021 10:03:50 -0500, Pavel Tatashin wrote:
> v3: - Sync with linux-next where arch_get_mappable_range() was
> introduced.
> v2: - Added test-by Tyler Hicks
> - Addressed comments from Anshuman Khandual: moved check under
> IS_ENABLED(CONFIG_RANDOMIZE_BASE), added
> WARN_ON(start_linear_pa > end_linear_pa);
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: mm: correct the inside linear map range during hotplug check
https://git.kernel.org/arm64/c/ee7febce0519
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-03-22 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 15:03 [PATCH v3 0/1] correct the inside linear map range during hotplug check Pavel Tatashin
2021-02-16 15:03 ` [PATCH v3 1/1] arm64: mm: " Pavel Tatashin
2021-02-19 19:18 ` Will Deacon
2021-02-19 19:44 ` Pavel Tatashin
2021-02-22 12:25 ` Will Deacon
2021-02-22 14:17 ` Pavel Tatashin
2021-03-19 15:43 ` Pavel Tatashin
2021-02-24 7:12 ` Anshuman Khandual
2021-03-22 13:19 ` Will Deacon [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=161641726115.3901166.7580035330760911434.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jmorris@namei.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=mhocko@suse.com \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=tyhicks@linux.microsoft.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;
as well as URLs for NNTP newsgroup(s).