From: Lance Yang <lance.yang@linux.dev>
To: ljs@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,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] MAINTAINERS: remove myself as THP co-maintainer
Date: Wed, 26 Aug 2026 20:43:16 +0800 [thread overview]
Message-ID: <20260826124316.80455-1-lance.yang@linux.dev> (raw)
In-Reply-To: <ao7Nr_FALfP7cTY5@gremlin>
On Wed, Aug 26, 2026 at 12:31:09PM +0100, Lorenzo Stoakes (ARM) wrote:
>Since it's 2026 :) I asked Claude to look at my time as THP co-maintainer:
>
> ~107,000 words of review across 948 emails (in 279 distinct
> threads), counting only prose you actually wrote — quoted text,
> signatures and attribution lines stripped. That's a full novel's
> worth of review commentary.
>
> Along the way you handed out 194 Reviewed-by and 15 Acked-by tags,
> and your longest single review was 2,404 words (mTHP collapse
> support, v12 — the khugepaged/mTHP collapse saga accounts for most
> of your top-10 longest reviews).
>
> Estimated review time: roughly 300–500 hours, centred around ~400
> (i.e. ~7 hours/week for 14 months).
>
> 1,615 THP-related emails in the window: 948 reviews of others'
> work, 278 replies on your own THP-touching series threads (~31k
> more words responding to review), 382 patch emails, and a handful
> of MAINTAINERS bits. Busiest months: March 2026 (131 review
> emails), June 2026 (113), August 2026 (111); quietest was December
> 2025 (5).
>
>Think I can be happy with that!
Aw, man ... I totally get needing to step back, but we can't let you
disappear from THP that easily :) You've put a crazy amount of time
into it, and your reviews and judgment have made a massive difference.
We'd miss you badly.
Could we talk you into staying on as a reviewer for now? Zero pressure to
keep up with everything or carry the maintainer load. Just hang around,
jump in whenever you feel like it, and come straight back as a maintainer
whenever life gives you the room.
Seriously, Lorenzo, THP still needs you. Please stick around!
Thanks, Lance
next prev parent reply other threads:[~2026-08-26 12:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 9:56 Lorenzo Stoakes (ARM)
2026-08-26 10:09 ` David Hildenbrand (Arm)
2026-08-26 10:23 ` Lorenzo Stoakes (ARM)
2026-08-26 14:32 ` Zi Yan
2026-08-27 13:00 ` Lorenzo Stoakes (ARM)
2026-08-26 11:31 ` Lorenzo Stoakes (ARM)
2026-08-26 12:43 ` Lance Yang [this message]
2026-08-26 13:28 ` Lorenzo Stoakes (ARM)
2026-08-27 8:23 ` Lian Wang (ProcessMission)
2026-08-27 13:06 ` Lorenzo Stoakes (ARM)
2026-08-27 8:38 ` Baolin Wang
2026-08-27 12:54 ` Lorenzo Stoakes (ARM)
2026-08-27 14:15 ` Usama Arif
2026-08-27 14:25 ` Lorenzo Stoakes (ARM)
2026-08-27 15:17 ` Usama Arif
2026-08-28 6:34 ` Vernon Yang
2026-08-28 7:06 ` Lorenzo Stoakes (ARM)
2026-08-26 12:04 ` Kiryl Shutsemau
2026-08-26 12:52 ` David Hildenbrand (Arm)
2026-08-27 13:07 ` Lorenzo Stoakes (ARM)
2026-08-26 21:02 ` Barry Song
2026-08-27 7:37 ` Lorenzo Stoakes (ARM)
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=20260826124316.80455-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=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
all inboxes | Powered by JetHome®