From: Lance Yang <lance.yang@linux.dev>
To: kas@kernel.org
Cc: akpm@linux-foundation.org, david@kernel.org, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, liam@infradead.org,
nico.pache@linux.dev, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, usama.arif@linux.dev,
ljs@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add myself as a THP reviewer
Date: Thu, 27 Aug 2026 19:46:08 +0800 [thread overview]
Message-ID: <20260827114608.4342-1-lance.yang@linux.dev> (raw)
In-Reply-To: <20260827103435.1371882-1-kas@kernel.org>
On Thu, Aug 27, 2026 at 11:34:35AM +0100, Kiryl Shutsemau (Meta) wrote:
>I have been working on transparent hugepages since 2012, starting with
>the huge zero page and file-backed THP. A lot of the code that causes
>pain now traces back to me. It is only fair if I share the review load
>for THP.
>
>Add myself to the reviewer list so get_maintainer.pl puts me on Cc: as
>well. It is also my commitment to be more active in reviewing this
>code.
>
>Signed-off-by: Kiryl Shutsemau (Meta) <kas@kernel.org>
>---
Welcome back to the THP party, Kiryl! :)
Reviewed-by: Lance Yang <lance.yang@linux.dev>
next prev parent reply other threads:[~2026-08-27 11:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 10:34 [PATCH] MAINTAINERS: add myself as a THP reviewer Kiryl Shutsemau (Meta)
2026-08-27 10:53 ` David Hildenbrand (Arm)
2026-08-27 11:19 ` Lorenzo Stoakes (ARM)
2026-08-27 11:23 ` Barry Song
2026-08-27 11:25 ` Zi Yan
2026-08-27 11:46 ` Lance Yang [this message]
2026-08-27 14:16 ` Usama Arif
2026-08-28 0:32 ` Baolin Wang
2026-08-28 0:42 ` SJ Park
-- strict thread matches above, loose matches on Subject: below --
2025-06-09 0:24 Barry Song
2025-06-09 1:34 ` Zi Yan
2025-06-09 3:08 ` Baolin Wang
2025-06-09 5:03 ` Dev Jain
2025-06-09 5:21 ` Lorenzo Stoakes
2025-06-09 11:11 ` Ryan Roberts
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=20260827114608.4342-1-lance.yang@linux.dev \
--to=lance.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=kas@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=nico.pache@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=usama.arif@linux.dev \
--cc=ziy@nvidia.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