From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
"Will Deacon" <will@kernel.org>,
"Dan Williams" <dan.j.williams@intel.com>,
"James Morse" <james.morse@arm.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"Veronika Kabatova" <vkabatov@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Mike Rapoport" <rppt@linux.ibm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Jérôme Glisse" <jglisse@redhat.com>
Subject: Re: [PATCH V3 0/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory
Date: Mon, 8 Mar 2021 19:16:00 +0000 [thread overview]
Message-ID: <161522664065.2443375.11063143181620758255.b4-ty@kernel.org> (raw)
In-Reply-To: <1614921898-4099-1-git-send-email-anshuman.khandual@arm.com>
On Fri, 5 Mar 2021 10:54:56 +0530, Anshuman Khandual wrote:
> This series fixes pfn_valid() for ZONE_DEVICE based memory and also improves
> its performance for normal hotplug memory. While here, it also reorganizes
> pfn_valid() on CONFIG_SPARSEMEM. This series is based on v5.12-rc1.
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: James Morse <james.morse@arm.com>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Jérôme Glisse <jglisse@redhat.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: David Hildenbrand <david@redhat.com>
> Cc: Mike Rapoport <rppt@linux.ibm.com>
> Cc: Veronika Kabatova <vkabatov@redhat.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-mm@kvack.org
> Cc: linux-kernel@vger.kernel.org
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory
https://git.kernel.org/arm64/c/eeb0753ba27b
[2/2] arm64/mm: Reorganize pfn_valid()
https://git.kernel.org/arm64/c/093bbe211ea5
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2021-03-08 19:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 5:24 Anshuman Khandual
2021-03-05 5:24 ` [PATCH V3 1/2] " Anshuman Khandual
2021-03-05 18:13 ` Catalin Marinas
2021-03-05 18:24 ` David Hildenbrand
2021-03-08 11:29 ` Catalin Marinas
2021-03-08 17:59 ` Catalin Marinas
2021-03-05 5:24 ` [PATCH V3 2/2] arm64/mm: Reorganize pfn_valid() Anshuman Khandual
2021-03-08 18:00 ` Catalin Marinas
2021-03-05 5:38 ` [PATCH V3 0/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory Anshuman Khandual
[not found] ` <2001895867.30197818.1614947320141.JavaMail.zimbra@redhat.com>
2021-03-05 18:16 ` Veronika Kabatova
2021-03-05 18:22 ` Catalin Marinas
2021-03-08 19:16 ` 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=161522664065.2443375.11063143181620758255.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=james.morse@arm.com \
--cc=jglisse@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--cc=rppt@linux.ibm.com \
--cc=vkabatov@redhat.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