All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Yoo <harry.yoo@oracle.com>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Hao Li <hao.li@linux.dev>, Christoph Lameter <cl@linux.com>,
	David Rientjes <rientjes@google.com>,
	Roman Gushchin <roman.gushchin@linux.dev>
Subject: Re: [PATCH] MAINTAINERS: add co-maintainer and reviewer for SLAB ALLOCATOR
Date: Mon, 2 Mar 2026 20:04:23 +0900	[thread overview]
Message-ID: <aaVut1GXyhPBXQs3@hyeyoo> (raw)
In-Reply-To: <aaVpbl7Om6aImsMo@hyeyoo>

On Mon, Mar 02, 2026 at 07:41:50PM +0900, Harry Yoo wrote:
> 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.
> 
> It's been my pleasure to get involved with folks in the slab subsystem
> over the years, and I'm happy to continue to do so!

I'd also like to thank Vlastimil, who has given me kind and constructive
feedback ever since I first started contributing to the kernel, five
years ago.

Back in 2021, I was a curious computer science undergrad with little
experience in kernel development, who decided to do something fun in the
kernel and sent a few patches to the slab subsystem. The first few
interactions with Vlastimil, who was generous with his feedback,
motivated me to keep contributing to the kernel as a hobby.

Through the discussions and collaboration we've had, I feel I've grown
into a better engineer. I'm glad that this growth has allowed me to
give back to the community as a contributor and now as a maintainer.

And this is all thanks to you, Vlastimil ;)

-- 
Cheers,
Harry / Hyeonggon


  reply	other threads:[~2026-03-02 11:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 10:13 [PATCH] MAINTAINERS: add co-maintainer and reviewer for SLAB ALLOCATOR Vlastimil Babka (SUSE)
2026-03-02 10:38 ` Lorenzo Stoakes
2026-03-02 10:41 ` Harry Yoo
2026-03-02 11:04   ` Harry Yoo [this message]
2026-03-05  9:37     ` Vlastimil Babka (SUSE)
2026-03-02 13:39 ` Hao Li
2026-03-05  9:39   ` Vlastimil Babka (SUSE)
2026-03-03  1:00 ` SeongJae Park

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=aaVut1GXyhPBXQs3@hyeyoo \
    --to=harry.yoo@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.