mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harry Yoo <harry@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: 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 18:10:35 +0900	[thread overview]
Message-ID: <e1738d98-a063-4bfd-8c98-ad4b449669bd@kernel.org> (raw)
In-Reply-To: <20260525-maint-slab-tools-v1-1-d66b69f1412a@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 936 bytes --]



On 5/25/26 4:26 PM, Vlastimil Babka (SUSE) 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>
> ---
>   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
>   
>   SLCAN CAN NETWORK DRIVER
>   M:	Dario Binacchi <dario.binacchi@amarulasolutions.com>
> 
> ---
Acked-by: Harry Yoo (Oracle) <harry@kernel.org>

-- 
Cheers,
Harry / Hyeonggon


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 265 bytes --]

  reply	other threads:[~2026-05-25  9:10 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 [this message]
2026-05-25 18:09 ` SeongJae Park
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=e1738d98-a063-4bfd-8c98-ad4b449669bd@kernel.org \
    --to=harry@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@gentwo.org \
    --cc=hao.li@linux.dev \
    --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