From: Nhat Pham <nphamcs@gmail.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Yu Zhao <yuzhao@google.com>,
Kemeng Shi <shikemeng@huaweicloud.com>,
Kairui Song <kasong@tencent.com>, Baoquan He <bhe@redhat.com>,
Barry Song <baohua@kernel.org>, Chris Li <chrisl@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: add mm swap section
Date: Mon, 2 Jun 2025 09:54:49 -0700 [thread overview]
Message-ID: <CAKEwX=Pd7HO3UbwYNWEeVOpw_q75sO2-Xqvgm_zM31pD3AfmOg@mail.gmail.com> (raw)
In-Reply-To: <20250602152015.54366-1-lorenzo.stoakes@oracle.com>
On Mon, Jun 2, 2025 at 8:20 AM Lorenzo Stoakes
<lorenzo.stoakes@oracle.com> wrote:
>
> In furtherance of ongoing efforts to ensure people are aware of who
> de-facto maintains/has an interest in specific parts of mm, as well trying
> to avoid get_maintainers.pl listing only Andrew and the mailing list for
> mm files - establish a swap memory management section and add relevant
> maintainers/reviewers.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
> REVIEWERS NOTE:
>
> I have taken a look at recent work on the swap and chosen a list of people
> who seem to be regular and recent contributors/reviewers.
>
> Please let me know if I missed anybody, or if anybody doesn't wish to be
> added here.
>
> I also realise we have a bunch of non-swap stuff living in some of these
> files - we will have to address this separately :)
>
> Thanks!
>
> MAINTAINERS | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e66460861bdf..3386272f6bf4 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15674,6 +15674,25 @@ S: Maintained
> F: include/linux/secretmem.h
> F: mm/secretmem.c
>
> +MEMORY MANAGEMENT - SWAP
> +M: Andrew Morton <akpm@linux-foundation.org>
> +R: Yu Zhao <yuzhao@google.com>
> +R: Kemeng Shi <shikemeng@huaweicloud.com>
> +R: Kairui Song <kasong@tencent.com>
> +R: Nhat Pham <nphamcs@gmail.com>
I'm honored, and would gladly help review swap patches :)
Acked-by: Nhat Pham <nphamcs@gmail.com>
> +R: Baoquan He <bhe@redhat.com>
> +R: Barry Song <baohua@kernel.org>
> +R: Chris Li <chrisl@kernel.org>
> +L: linux-mm@kvack.org
> +S: Maintained
> +F: include/linux/swap.h
> +F: include/linux/swapfile.h
> +F: include/linux/swapops.h
> +F: mm/swap.c
> +F: mm/swap.h
> +F: mm/swap_state.c
> +F: mm/swapfile.c
> +
> MEMORY MANAGEMENT - THP (TRANSPARENT HUGE PAGE)
> M: Andrew Morton <akpm@linux-foundation.org>
> M: David Hildenbrand <david@redhat.com>
> --
> 2.49.0
next prev parent reply other threads:[~2025-06-02 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 15:20 Lorenzo Stoakes
2025-06-02 16:54 ` Nhat Pham [this message]
2025-06-02 21:36 ` Barry Song
2025-06-02 23:52 ` Nhat Pham
2025-06-03 11:52 ` Lorenzo Stoakes
2025-06-03 0:20 ` Baoquan He
2025-06-03 11:52 ` Lorenzo Stoakes
2025-06-03 1:17 ` Kemeng Shi
2025-06-03 1:57 ` Andrew Morton
2025-06-03 7:20 ` Hugh Dickins
2025-06-03 12:18 ` David Hildenbrand
2025-06-03 2:50 ` Kairui Song
2025-06-03 20:29 ` Chris Li
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='CAKEwX=Pd7HO3UbwYNWEeVOpw_q75sO2-Xqvgm_zM31pD3AfmOg@mail.gmail.com' \
--to=nphamcs@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=bhe@redhat.com \
--cc=chrisl@kernel.org \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=shikemeng@huaweicloud.com \
--cc=yuzhao@google.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