From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH] MAINTAINERS: move memremap.[ch] to hotplug section
Date: Tue, 22 Jul 2025 21:52:21 +0200 [thread overview]
Message-ID: <883296f4-ec25-4961-aafb-b2ccb1607422@redhat.com> (raw)
In-Reply-To: <20250722172258.143488-1-lorenzo.stoakes@oracle.com>
On 22.07.25 19:22, Lorenzo Stoakes wrote:
> This seems to be the most appropriate place for these files.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
> MAINTAINERS | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 837bc5cd6166..68b8407926a6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15729,6 +15729,8 @@ F: Documentation/admin-guide/mm/memory-hotplug.rst
> F: Documentation/core-api/memory-hotplug.rst
> F: drivers/base/memory.c
> F: include/linux/memory_hotplug.h
> +F: include/linux/memremap.h
> +F: mm/memremap.c
> F: mm/memory_hotplug.c
> F: tools/testing/selftests/memory-hotplug/
>
> @@ -15747,7 +15749,6 @@ F: include/linux/memory_hotplug.h
> F: include/linux/memory-tiers.h> F: include/linux/mempolicy.h
> F: include/linux/mempool.h
> -F: include/linux/memremap.h
> F: include/linux/mmzone.h
> F: include/linux/mmu_notifier.h
> F: include/linux/pagewalk.h
As discussed, alternatively some ZONE_DEVICE stuff.
But memory hotplug is fine with me as well
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-07-22 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 17:22 Lorenzo Stoakes
2025-07-22 17:25 ` Lorenzo Stoakes
2025-07-22 19:52 ` David Hildenbrand [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=883296f4-ec25-4961-aafb-b2ccb1607422@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=osalvador@suse.de \
/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