From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
James Morris <jmorris@namei.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Logan Gunthorpe <logang@deltatee.com>,
Tyler Hicks <tyhicks@linux.microsoft.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH v2 1/1] arm64: mm: correct the inside linear map boundaries during hotplug check
Date: Tue, 16 Feb 2021 09:48:35 -0500 [thread overview]
Message-ID: <CA+CK2bBRoXEHr+tPz4VH4JkjrhCfTxVi0Y_L8AtFV=o=aJt6sA@mail.gmail.com> (raw)
In-Reply-To: <73bf9ad0-37a9-78f4-3583-2845dcb24f34@arm.com>
> There is a new generic framework which expects the platform to provide two
> distinct range points (low and high) for hotplug address comparison. Those
> range points can be different depending on whether address randomization
> is enabled and the flip occurs. But this comparison here in the platform
> code is going away.
>
> This patch needs to rebased on the new framework which is part of linux-next.
>
> https://patchwork.kernel.org/project/linux-mm/list/?series=425051
Hi Anshuman,
Thanks for letting me know. I will send an updated patch against linux-next.
Thank you,
Pasha
_______________________________________________
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-02-16 14:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 19:22 [PATCH v2 0/1] correct the inside linear map boundaries during hotplug check Pavel Tatashin
2021-02-15 19:22 ` [PATCH v2 1/1] arm64: mm: " Pavel Tatashin
2021-02-15 19:27 ` Ard Biesheuvel
2021-02-15 19:30 ` Pavel Tatashin
2021-02-15 19:34 ` Ard Biesheuvel
2021-02-15 19:51 ` Pavel Tatashin
2021-02-15 22:28 ` Pavel Tatashin
2021-02-16 3:12 ` Anshuman Khandual
2021-02-16 7:36 ` Ard Biesheuvel
2021-02-16 14:34 ` Pavel Tatashin
2021-02-16 2:55 ` Anshuman Khandual
2021-02-16 14:48 ` Pavel Tatashin [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='CA+CK2bBRoXEHr+tPz4VH4JkjrhCfTxVi0Y_L8AtFV=o=aJt6sA@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jmorris@namei.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=rppt@kernel.org \
--cc=tyhicks@linux.microsoft.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).