All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Anshuman Khandual <anshuman.khandual@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	"Will Deacon" <will@kernel.org>,
	"David Hildenbrand" <david@redhat.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Robin Murphy" <robin.murphy@arm.com>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"Mike Rapoport" <rppt@linux.ibm.com>,
	"James Morse" <james.morse@arm.com>,
	"Dan Williams" <dan.j.williams@intel.com>
Subject: Re: [PATCH V2 0/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory
Date: Fri,  5 Feb 2021 18:52:50 +0000	[thread overview]
Message-ID: <161254816916.731861.2448215186785582734.b4-ty@kernel.org> (raw)
In-Reply-To: <1612239114-28428-1-git-send-email-anshuman.khandual@arm.com>

On Tue, 2 Feb 2021 09:41:52 +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.11-rc6.
> 
> Question - should pfn_section_valid() be tested both for boot and non boot
> memory as well ?
> 
> [...]

Applied to arm64 (for-next/mm), thanks!

[1/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory
      https://git.kernel.org/arm64/c/fccf0a3dfeaf
[2/2] arm64/mm: Reorganize pfn_valid()
      https://git.kernel.org/arm64/c/387f3531116e

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Anshuman Khandual <anshuman.khandual@arm.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
	"Will Deacon" <will@kernel.org>,
	"David Hildenbrand" <david@redhat.com>,
	catalin.marinas@arm.com, "Robin Murphy" <robin.murphy@arm.com>,
	"Mike Rapoport" <rppt@linux.ibm.com>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"James Morse" <james.morse@arm.com>,
	"Dan Williams" <dan.j.williams@intel.com>,
	kernel-team@android.com, "Ard Biesheuvel" <ardb@kernel.org>
Subject: Re: [PATCH V2 0/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory
Date: Fri,  5 Feb 2021 18:52:50 +0000	[thread overview]
Message-ID: <161254816916.731861.2448215186785582734.b4-ty@kernel.org> (raw)
In-Reply-To: <1612239114-28428-1-git-send-email-anshuman.khandual@arm.com>

On Tue, 2 Feb 2021 09:41:52 +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.11-rc6.
> 
> Question - should pfn_section_valid() be tested both for boot and non boot
> memory as well ?
> 
> [...]

Applied to arm64 (for-next/mm), thanks!

[1/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory
      https://git.kernel.org/arm64/c/fccf0a3dfeaf
[2/2] arm64/mm: Reorganize pfn_valid()
      https://git.kernel.org/arm64/c/387f3531116e

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

  parent reply	other threads:[~2021-02-05 18:54 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  4:11 [PATCH V2 0/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory Anshuman Khandual
2021-02-02  4:11 ` Anshuman Khandual
2021-02-02  4:11 ` [PATCH V2 1/2] " Anshuman Khandual
2021-02-02  4:11   ` Anshuman Khandual
2021-02-02 12:32   ` Will Deacon
2021-02-02 12:32     ` Will Deacon
2021-02-02 12:35     ` Will Deacon
2021-02-02 12:35       ` Will Deacon
2021-02-02 12:39       ` David Hildenbrand
2021-02-02 12:39         ` David Hildenbrand
2021-02-02 12:51         ` Will Deacon
2021-02-02 12:51           ` Will Deacon
2021-02-02 12:56           ` David Hildenbrand
2021-02-02 12:56             ` David Hildenbrand
2021-02-03  3:50             ` Anshuman Khandual
2021-02-03  3:50               ` Anshuman Khandual
2021-02-05 18:55               ` Will Deacon
2021-02-05 18:55                 ` Will Deacon
2021-02-11 11:53                 ` Will Deacon
2021-02-11 11:53                   ` Will Deacon
2021-02-11 12:10                   ` Anshuman Khandual
2021-02-11 12:10                     ` Anshuman Khandual
2021-02-11 12:21                     ` Will Deacon
2021-02-11 12:21                       ` Will Deacon
2021-02-11 12:35                     ` David Hildenbrand
2021-02-11 12:35                       ` David Hildenbrand
2021-03-03 19:04                       ` Catalin Marinas
2021-03-03 19:04                         ` Catalin Marinas
2021-03-03 19:24                         ` David Hildenbrand
2021-03-03 19:24                           ` David Hildenbrand
2021-03-03 21:24                         ` Will Deacon
2021-03-03 21:24                           ` Will Deacon
2021-03-04  3:31                           ` Anshuman Khandual
2021-03-04  3:31                             ` Anshuman Khandual
2021-03-04  8:12                             ` David Hildenbrand
2021-03-04  8:12                               ` David Hildenbrand
2021-03-04  9:36                               ` Will Deacon
2021-03-04  9:36                                 ` Will Deacon
2021-03-05  4:22                                 ` Anshuman Khandual
2021-03-05  4:22                                   ` Anshuman Khandual
2021-02-02  4:11 ` [PATCH V2 2/2] arm64/mm: Reorganize pfn_valid() Anshuman Khandual
2021-02-02  4:11   ` Anshuman Khandual
2021-02-02  8:26   ` David Hildenbrand
2021-02-02  8:26     ` David Hildenbrand
2021-02-05 18:52 ` Will Deacon [this message]
2021-02-05 18:52   ` [PATCH V2 0/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory Will Deacon

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=161254816916.731861.2448215186785582734.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 \
    /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.