From: SeongJae Park <sj@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: SeongJae Park <sj@kernel.org>, Harry Yoo <harry@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Hao Li <hao.li@linux.dev>,
Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-mm@kvack.org
Subject: Re: [PATCH slab] MAINTAINERS: add slab-related scripts and tools to SLAB ALLOCATOR
Date: Mon, 25 May 2026 11:09:40 -0700 [thread overview]
Message-ID: <20260525180940.10383-1-sj@kernel.org> (raw)
In-Reply-To: <20260525-maint-slab-tools-v1-1-d66b69f1412a@kernel.org>
On Mon, 25 May 2026 09:26:39 +0200 "Vlastimil Babka (SUSE)" <vbabka@kernel.org> wrote:
> Make sure the maintainers and reviewers are CC'd on changes to the
> scripts and tools that depend on slab internals.
>
> Signed-off-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
Acked-by: SeongJae Park <sj@kernel.org>
> ---
> MAINTAINERS | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 288866c32ade..9ee06cd35793 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -24555,6 +24555,12 @@ F: mm/mempool.c
> F: mm/slab.h
> F: mm/slab_common.c
> F: mm/slub.c
> +F: scripts/gdb/linux/slab.py
> +F: tools/cgroup/memcg_slabinfo.py
> +F: tools/include/linux/slab.h
> +F: tools/lib/slab.c
> +F: tools/mm/slabinfo-gnuplot.sh
> +F: tools/mm/slabinfo.c
>
I found there is rust/helpers/slab.c file and it is not in this section. Is it
intentional? I found commits for the file doesn't have Vlastimil's R-b or A-b
tags, so it might be intentional for rust code, but I'm just curious if that's
correct.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-05-25 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 7:26 Vlastimil Babka (SUSE)
2026-05-25 9:10 ` Harry Yoo
2026-05-25 18:09 ` SeongJae Park [this message]
2026-05-25 18:33 ` Vlastimil Babka (SUSE)
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=20260525180940.10383-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--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
Powered by JetHome