From: Hao Li <hao.li@linux.dev>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Harry Yoo <harry.yoo@oracle.com>,
Christoph Lameter <cl@linux.com>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [PATCH] MAINTAINERS: add co-maintainer and reviewer for SLAB ALLOCATOR
Date: Mon, 2 Mar 2026 21:39:58 +0800 [thread overview]
Message-ID: <qjsfacsbh2lkzhng77zl4xyknsjybxvsuqulbfegy5moac4za3@i5gg57ddh27n> (raw)
In-Reply-To: <20260302101345.36713-2-vbabka@kernel.org>
On Mon, Mar 02, 2026 at 11:13:46AM +0100, Vlastimil Babka (SUSE) wrote:
> Promote Harry Yoo from reviewer to maintainer. Harry's been involved in
> slab development for multiple years now and doing a great job.
Congrats, Harry! Well deserved. Looking forward to working with you in the new
role!
>
> Add Hao Li as a new reviewer. Hao has been doing very useful reviews for
> a while now, so make it official and ensure the Cc's.
Thanks, Vlastimil. I really appreciate the trust!
Also, thank you for the patient and constructive feedback and for taking the
time to engage with newer contributors like me on-list. I especially
appreciate you proactively Cc'ing me on relevant slab threads (even when I
wasn't on the original Cc). It helped me stay in the loop and get involved
more deeply. Happy to help with slab reviews going forward.
And thanks, Harry, for the kind words. I really appreciate the encouragement.
You were the first to Cc me on your slab patches and actively invite my input,
which really helped me feel involved and start contributing more. I've learned
a lot from our collaboration and look forward to continuing to work together.
Thanks also to Lorenzo for the congratulations.
Acked-by: Hao Li <hao.li@linux.dev>
>
> Signed-off-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
> ---
> MAINTAINERS | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 61bf550fd37c..5f3cc4193a8e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -24350,11 +24350,12 @@ F: drivers/nvmem/layouts/sl28vpd.c
>
> SLAB ALLOCATOR
> M: Vlastimil Babka <vbabka@kernel.org>
> +M: Harry Yoo <harry.yoo@oracle.com>
> M: Andrew Morton <akpm@linux-foundation.org>
> +R: Hao Li <hao.li@linux.dev>
> R: Christoph Lameter <cl@gentwo.org>
> R: David Rientjes <rientjes@google.com>
> R: Roman Gushchin <roman.gushchin@linux.dev>
> -R: Harry Yoo <harry.yoo@oracle.com>
> L: linux-mm@kvack.org
> S: Maintained
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git
> --
> 2.53.0
>
prev parent reply other threads:[~2026-03-02 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 10:13 Vlastimil Babka (SUSE)
2026-03-02 10:38 ` Lorenzo Stoakes
2026-03-02 10:41 ` Harry Yoo
2026-03-02 11:04 ` Harry Yoo
2026-03-02 13:39 ` Hao Li [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=qjsfacsbh2lkzhng77zl4xyknsjybxvsuqulbfegy5moac4za3@i5gg57ddh27n \
--to=hao.li@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--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