From: David Hildenbrand <david@redhat.com>
To: Joshua Hahn <joshua.hahnjy@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Zi Yan <ziy@nvidia.com>, Matthew Brost <matthew.brost@intel.com>,
Rakie Kim <rakie.kim@sk.com>, Byungchul Park <byungchul@sk.com>,
Gregory Price <gourry@gourry.net>,
Ying Huang <ying.huang@linux.alibaba.com>,
Alistair Popple <apopple@nvidia.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel-team@meta.com
Subject: Re: [PATCH] MAINTAINERS: Add missing headers to mempory policy & migration section
Date: Fri, 25 Jul 2025 20:03:09 +0200 [thread overview]
Message-ID: <d546df23-70df-47a2-9211-2bb971f8834b@redhat.com> (raw)
In-Reply-To: <20250725175616.2397031-1-joshua.hahnjy@gmail.com>
On 25.07.25 19:56, Joshua Hahn wrote:
> These two files currently do not belong to any section.
> The memory policy & migration section seems to be a good home for them!
>
> Signed-off-by: Joshua Hahn <joshua.hahnjy@gmail.com>
> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a8bebd0886df..dec8db8b5cc7 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15838,7 +15838,9 @@ S: Maintained
> W: http://www.linux-mm.org
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> F: include/linux/mempolicy.h
> +F: include/uapi/linux/mempolicy.h
That one is already on that secion on the mm/mm-new branch
> F: include/linux/migrate.h
> +F: include/linux/migrate_mode.h
Yeah, that one is missing.
Can you rebase to mm/mm-new? Thanks!
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-07-25 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 17:56 [PATCH] MAINTAINERS: Add missing headers to mempory policy & migration section Joshua Hahn
2025-07-25 18:03 ` David Hildenbrand [this message]
2025-07-25 18:17 ` Joshua Hahn
2025-07-25 18:23 ` David Hildenbrand
2025-07-25 18:27 ` Joshua Hahn
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=d546df23-70df-47a2-9211-2bb971f8834b@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=matthew.brost@intel.com \
--cc=rakie.kim@sk.com \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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).