From: Vlastimil Babka <vbabka@suse.cz>
To: linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: [PATCH] MAINTAINERS: add myself as slab allocators maintainer
Date: Fri, 8 Jan 2021 12:03:53 +0100 [thread overview]
Message-ID: <20210108110353.19971-1-vbabka@suse.cz> (raw)
I would like to help with slab allocators maintenance, from the perspective of
being responsible for SLAB and more recently also SLUB in an enterprise distro
kernel and supporting its users. Recently I've been focusing on improving
SLUB's debugging features, and patch review in the area, including the kmemcg
accounting rewrite last year.
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
---
Hi,
this might look perhaps odd with 4 people (plus Andrew) already listed, but on
closer look we have 2 (or 3 if you count SLOB) allocators and the focus of each
maintainer varies. Maybe this would be also an opportunity to split the area
explicitly, if the maintainers would want that? I'm fine with all of them
personally - while we moved to SLUB in new code streams, olders ones with SLAB
will continue be supported for years anyway.
Thanks,
Vlastimil
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index da4892dc52b4..fd657bb4157f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16351,6 +16351,7 @@ M: Pekka Enberg <penberg@kernel.org>
M: David Rientjes <rientjes@google.com>
M: Joonsoo Kim <iamjoonsoo.kim@lge.com>
M: Andrew Morton <akpm@linux-foundation.org>
+M: Vlastimil Babka <vbabka@suse.cz>
L: linux-mm@kvack.org
S: Maintained
F: include/linux/sl?b*.h
--
2.29.2
next reply other threads:[~2021-01-08 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 11:03 Vlastimil Babka [this message]
2021-01-08 18:46 ` Christoph Lameter
2021-01-14 13:17 ` Vlastimil Babka
2021-01-15 9:03 ` David Rientjes
2021-01-15 12:45 ` Vlastimil Babka
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=20210108110353.19971-1-vbabka@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@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