linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Jann Horn <jannh@google.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: Wed, 9 Apr 2025 06:17:21 +0100	[thread overview]
Message-ID: <4c085979-0f6c-463d-86c4-456634a1bb89@lucifer.local> (raw)
In-Reply-To: <CAG48ez1duuiePx2pFnTuQK8WEEdKGM4AYCYjDb0XLpJBzNT1=A@mail.gmail.com>

On Tue, Apr 08, 2025 at 08:56:30PM +0200, Jann Horn wrote:
> 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>

Thanks!

>
> > +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?

No, was a mistake, have asked Andrew to fix in a fixpatch! Good
spot... whoops!


      reply	other threads:[~2025-04-09  5:17 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
2025-04-09  5:17   ` Lorenzo Stoakes [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=4c085979-0f6c-463d-86c4-456634a1bb89@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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