From: "Christoph Lameter (Ampere)" <cl@gentwo.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Harry Yoo <harry.yoo@oracle.com>
Subject: Re: [PATCH 10/10] slab: Fix MAINTAINERS entry
Date: Mon, 9 Jun 2025 09:42:37 -0700 (PDT) [thread overview]
Message-ID: <5b81c709-7a89-6065-422d-3148aebc78e9@gentwo.org> (raw)
In-Reply-To: <d679fe2b-68ff-45ce-bfe5-60139cc082aa@lucifer.local>
On Mon, 9 Jun 2025, Lorenzo Stoakes wrote:
> Informally, as discussed at LSF/MM, the broad perception is that a
> maintainer MUST be actively involved, whereas a reviewer has expertise and
> MAY optionally get involved in the process.
Both Andrew and I are actively involved in various ways but we have other
priorities as well. If there would be an issue with maintainership then we
would address the issue.
> I base this on the fact that Christoph has made 2 patches (other than
> updating email) since 2020 and David hasn't contributed patches since 2016
> (please forgive me if I missed anything, this was a _rough_ git log check).
The two patches were in 2024 and there was one in 2020.... The last
large scale change I did to slab was in 2015. If you look at Andrew's
changes its a similar thing.
> Whereas Vlastimil has essentially handled _all_ slab maintainership duties
> for a very long time.
Yes he is doing a great job and has done so for a long time. That is one
reason why we can spend more time with other things and limit ourselves to
mostly commenting here and there.
> According to the maintainer handbook [0]:
>
> "That said, being a maintainer is an active role. The MAINTAINERS
> file is not a list of credits (in fact a separate CREDITS file
> exists), it is a list of those who will actively help with the
> code. If the author does not have the time, interest or ability to
> maintain the code, a different maintainer must be selected."
Well both Andrew and I fit that role as maintainers.
next prev parent reply other threads:[~2025-06-09 16:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 22:22 [PATCH 00/10] Various slab improvements Matthew Wilcox (Oracle)
2025-06-06 22:22 ` [PATCH 01/10] doc: Move SLUB documentation to the admin guide Matthew Wilcox (Oracle)
2025-06-09 1:42 ` Harry Yoo
2025-06-09 12:13 ` Vlastimil Babka
2025-06-06 22:22 ` [PATCH 02/10] slab: Rename slab->__page_flags to slab->flags Matthew Wilcox (Oracle)
2025-06-09 2:15 ` Harry Yoo
2025-06-09 12:45 ` Matthew Wilcox
2025-06-09 13:12 ` Vlastimil Babka
2025-06-06 22:22 ` [PATCH 03/10] slab: Add SL_private flag Matthew Wilcox (Oracle)
2025-06-09 2:25 ` Harry Yoo
2025-06-06 22:22 ` [PATCH 04/10] slab: Add SL_pfmemalloc flag Matthew Wilcox (Oracle)
2025-06-09 2:27 ` Harry Yoo
2025-06-06 22:22 ` [PATCH 05/10] doc: Add slab internal kernel-doc Matthew Wilcox (Oracle)
2025-06-09 2:37 ` Harry Yoo
2025-06-09 15:22 ` Matthew Wilcox
2025-06-06 22:22 ` [PATCH 06/10] vmcoreinfo: Remove documentation of PG_slab and PG_hugetlb Matthew Wilcox (Oracle)
2025-06-09 2:44 ` Harry Yoo
2025-06-06 22:22 ` [PATCH 07/10] proc: Remove mention of PG_slab Matthew Wilcox (Oracle)
2025-06-06 22:22 ` [PATCH 08/10] kfence: " Matthew Wilcox (Oracle)
2025-06-09 3:42 ` Harry Yoo
2025-06-09 13:33 ` Vlastimil Babka
2025-06-09 15:02 ` Matthew Wilcox
2025-06-10 13:23 ` Marco Elver
2025-06-06 22:22 ` [PATCH 09/10] memcg_slabinfo: Fix use " Matthew Wilcox (Oracle)
2025-06-09 3:08 ` Harry Yoo
2025-06-06 22:22 ` [PATCH 10/10] slab: Fix MAINTAINERS entry Matthew Wilcox (Oracle)
2025-06-09 3:21 ` Harry Yoo
2025-06-09 13:38 ` Vlastimil Babka
2025-06-09 13:59 ` Lorenzo Stoakes
2025-06-09 16:42 ` Christoph Lameter (Ampere) [this message]
2025-06-09 17:44 ` Matthew Wilcox
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=5b81c709-7a89-6065-422d-3148aebc78e9@gentwo.org \
--to=cl@gentwo.org \
--cc=akpm@linux-foundation.org \
--cc=harry.yoo@oracle.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--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