From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Brian Masney <bmasney@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add vm.rst to memory management core
Date: Thu, 28 May 2026 18:26:10 -0700 [thread overview]
Message-ID: <20260529012611.8578-1-sj@kernel.org> (raw)
In-Reply-To: <20260529002525.7939-1-sj@kernel.org>
On Thu, 28 May 2026 17:25:24 -0700 SeongJae Park <sj@kernel.org> wrote:
> On Thu, 28 May 2026 09:56:14 -0400 Brian Masney <bmasney@redhat.com> wrote:
>
> > The vm.rst file is currently not listed in the MAINTAINERS file, so
> > let's go ahead and add to the MM core subsystem so that the maintainers
> > are CCed when changes to the documentation are proposed.
>
> Makes sense to me.
>
> Probably out of the scope of this patch, but would it make sense to also rename
> it to mm.rst, like we replaced many 'vm' parts of file names to 'mm', e.g.,
> commit ee65728e103b ("docs: rename Documentation/vm to Documentation/mm") in
> future?
Reading above again, I think I wrote it in a confusing way, sorry.
I mean, it is "definitely" out of the scope of this patch. I'm not asking
Brian to do such renaming. I'm just loudly wondering if such renaming is
somewhat worthy to do in future.
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-05-29 1:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 13:56 [PATCH] MAINTAINERS: add vm.rst to memory management core Brian Masney
2026-05-28 13:59 ` Lorenzo Stoakes
2026-05-28 14:06 ` Oscar Salvador (SUSE)
2026-05-28 19:12 ` Liam R. Howlett
2026-05-29 0:25 ` SeongJae Park
2026-05-29 1:26 ` SeongJae Park [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=20260529012611.8578-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bmasney@redhat.com \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.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