mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: 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 20:33:13 +0200	[thread overview]
Message-ID: <9787578f-91ee-4f37-b13c-26c447db8f5e@kernel.org> (raw)
In-Reply-To: <20260525180940.10383-1-sj@kernel.org>

On 5/25/26 20:09, SeongJae Park wrote:
> 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.

Yeah, thanks. AFAIK these are just thin wrappers to overcome some bindgen
details? I think whatever the rust side finds necessary to do there, they
can and it's under RUST section, while the tools had no maintainer at all.
So we don't need to cross-maintain that.

      reply	other threads:[~2026-05-25 18:33 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
2026-05-25 18:33   ` Vlastimil Babka (SUSE) [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=9787578f-91ee-4f37-b13c-26c447db8f5e@kernel.org \
    --to=vbabka@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=sj@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