From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <kees@kernel.org>, David Hildenbrand <david@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add kernel/fork.c to relevant sections
Date: Tue, 13 May 2025 11:55:15 -0400 [thread overview]
Message-ID: <m55uzgmytniwkxv6k22xyw6jrh4o4ya2mimsacnblvgi6d463b@r3vd54totw6s> (raw)
In-Reply-To: <20250513145706.122101-1-lorenzo.stoakes@oracle.com>
* Lorenzo Stoakes <lorenzo.stoakes@oracle.com> [250513 10:57]:
> Currently kernel/fork.c both contains absolutely key logic relating to a
> number of kernel subsystems and also has absolutely no assignment in
> MAINTAINERS.
>
> Correct this by placing this file in relevant sections - mm core, exec and
> the scheduler so people know who to contact when making changes here.
>
> scripts/get_maintainers.pl can perfectly well handle a file being in
> multiple sections, so this functions correctly.
>
> Intent is that we keep putting changes to kernel/fork.c through Andrew's
> tree.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Acked-by: Michal Hocko <mhocko@suse.com>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> Reviewed-by: Kees Cook <kees@kernel.org>
> Acked-by: David Hildenbrand <david@redhat.com>
Acked-by: Liam R. Howlett <Liam.Howlett@oracle.com>
> ---
> MAINTAINERS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ff5d3c40e749..d4092ebfbe03 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8838,6 +8838,7 @@ F: include/linux/elf.h
> F: include/uapi/linux/auxvec.h
> F: include/uapi/linux/binfmts.h
> F: include/uapi/linux/elf.h
> +F: kernel/fork.c
> F: mm/vma_exec.c
> F: tools/testing/selftests/exec/
> N: asm/elf.h
> @@ -15539,6 +15540,7 @@ F: include/linux/mm.h
> F: include/linux/mm_*.h
> F: include/linux/mmdebug.h
> F: include/linux/pagewalk.h
> +F: kernel/fork.c
> F: mm/Kconfig
> F: mm/debug.c
> F: mm/init-mm.c
> @@ -21769,6 +21771,7 @@ F: include/linux/preempt.h
> F: include/linux/sched.h
> F: include/linux/wait.h
> F: include/uapi/linux/sched.h
> +F: kernel/fork.c
> F: kernel/sched/
>
> SCHEDULER - SCHED_EXT
> --
> 2.49.0
>
prev parent reply other threads:[~2025-05-13 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 14:57 Lorenzo Stoakes
2025-05-13 15:55 ` Liam R. Howlett [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=m55uzgmytniwkxv6k22xyw6jrh4o4ya2mimsacnblvgi6d463b@r3vd54totw6s \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bsegall@google.com \
--cc=david@redhat.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@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