From: Jann Horn <jannh@google.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add memory advice section
Date: Tue, 8 Apr 2025 20:56:30 +0200 [thread overview]
Message-ID: <CAG48ez1duuiePx2pFnTuQK8WEEdKGM4AYCYjDb0XLpJBzNT1=A@mail.gmail.com> (raw)
In-Reply-To: <20250408161105.156350-1-lorenzo.stoakes@oracle.com>
On Tue, Apr 8, 2025 at 6:11 PM Lorenzo Stoakes
<lorenzo.stoakes@oracle.com> wrote:
> The madvise code straddles both VMA and page table manipulation. As a
> result, separate it out into its own section and add maintainers/reviewers
> as appropriate.
>
> We additionally include the mman-common.h file as this contains the shared
> madvise flags and it is important we maintain this alongside madvise.c.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Acked-by: Jann Horn <jannh@google.com>
> +MEMORY MAPPING - MEMORY ADVICE
> +M: Andrew Morton <akpm@linux-foundation.org>
> +M: Liam R. Howlett <Liam.Howlett@oracle.com>
> +M: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> +M: David Hildenbrand <david@redhat.com>
> +R: Vlastimil Babka <vbabka@suse.cz>
> +R: Jann Horn <jannh@google.com>
> +S: Maintained
> +W: http://www.linux-mm.org
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> +F: include/uapi/asm-generic/mman-common.h
> +F: mm/madvise.c
Is it intentional that this one, unlike "MEMORY MAPPING", has no
explicit "L: linux-mm@kvack.org" and relies on the inheritance from
the overall "MEMORY MANAGEMENT" entry for that?
next prev parent reply other threads:[~2025-04-08 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 16:11 Lorenzo Stoakes
2025-04-08 17:00 ` Liam R. Howlett
2025-04-08 17:15 ` Vlastimil Babka
2025-04-08 21:19 ` Andrew Morton
2025-04-09 5:16 ` Lorenzo Stoakes
2025-04-09 5:20 ` Lorenzo Stoakes
2025-04-08 18:47 ` David Hildenbrand
2025-04-08 18:56 ` Jann Horn [this message]
2025-04-09 5:17 ` Lorenzo Stoakes
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='CAG48ez1duuiePx2pFnTuQK8WEEdKGM4AYCYjDb0XLpJBzNT1=A@mail.gmail.com' \
--to=jannh@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=vbabka@suse.cz \
/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