linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, "Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Matthew Wilcox <willy@infradead.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Eric Biederman <ebiederm@xmission.com>,
	Kees Cook <kees@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH 5/7] MAINTAINERS: Add entry for new VMA files
Date: Thu, 4 Jul 2024 10:49:01 +0100	[thread overview]
Message-ID: <f4199b5f-8cfc-46a5-b985-34db03fcf7a9@lucifer.local> (raw)
In-Reply-To: <a2d9d43b-9cc3-4668-8c87-46da90bd8752@suse.cz>

On Thu, Jul 04, 2024 at 09:39:14AM GMT, Vlastimil Babka wrote:
> On 7/3/24 1:57 PM, Lorenzo Stoakes wrote:
> > The vma files contain logic split from mmap.c for the most part and are all
> > relevant to VMA logic, so maintain the same reviewers for both.
>
> But it's still related to mmap.c a lot, so why not just rename that existing
> "MEMORY MAPPING" appropriately (how? haha) and expand it with the new files?

Yeah it's debatable, but I think going forward we may wish to to further
separate the concept of memory mapping logic and VMA manipulation in which
case it makes sense to keep them separated :)

>
> > Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > ---
> >  MAINTAINERS | 13 +++++++++++++
> >  1 file changed, 13 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 098d214f78d9..ff3e113ed081 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -23971,6 +23971,19 @@ F:	include/uapi/linux/vsockmon.h
> >  F:	net/vmw_vsock/
> >  F:	tools/testing/vsock/
> >
> > +VMA
> > +M:	Andrew Morton <akpm@linux-foundation.org>
> > +R:	Liam R. Howlett <Liam.Howlett@oracle.com>
> > +R:	Vlastimil Babka <vbabka@suse.cz>
> > +R:	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > +L:	linux-mm@kvack.org
> > +S:	Maintained
> > +W:	https://www.linux-mm.org
> > +T:	git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> > +F:	mm/vma.c
> > +F:	mm/vma.h
> > +F:	mm/vma_internal.h
> > +
> >  VMALLOC
> >  M:	Andrew Morton <akpm@linux-foundation.org>
> >  R:	Uladzislau Rezki <urezki@gmail.com>
> > --
> > 2.45.2
>


  reply	other threads:[~2024-07-04  9:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 11:57 [PATCH 0/7] Make core VMA operations internal and testable Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 1/7] userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 2/7] mm: move vma_modify() and helpers to internal header Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 3/7] mm: move vma_shrink(), vma_expand() " Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 4/7] mm: move internal core VMA manipulation functions to own file Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 5/7] MAINTAINERS: Add entry for new VMA files Lorenzo Stoakes
2024-07-04  7:39   ` Vlastimil Babka
2024-07-04  9:49     ` Lorenzo Stoakes [this message]
2024-07-03 11:57 ` [PATCH 6/7] tools: separate out shared radix-tree components Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 7/7] tools: add skeleton code for userland testing of VMA logic Lorenzo Stoakes
2024-07-04  5:59   ` SeongJae Park
2024-07-04 10:51     ` Lorenzo Stoakes
2024-07-04 11:44   ` Lorenzo Stoakes
2024-07-03 20:26 ` [PATCH 0/7] Make core VMA operations internal and testable Andrew Morton
2024-07-03 20:33   ` Lorenzo Stoakes
2024-07-03 21:43     ` Andrew Morton
2024-07-03 22:56     ` SeongJae Park
2024-07-03 23:24       ` Lorenzo Stoakes
2024-07-04  0:31         ` SeongJae Park
2024-07-04  1:26         ` Andrew Morton
2024-07-04  7:10       ` David Gow
2024-07-04 10:18         ` 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=f4199b5f-8cfc-46a5-b985-34db03fcf7a9@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=jack@suse.cz \
    --cc=kees@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    /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