All of lore.kernel.org
 help / color / mirror / Atom feed
From: Usama Arif <usama.arif@linux.dev>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>, Zi Yan <ziy@nvidia.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	"Liam R. Howlett" <liam@infradead.org>,
	Nico Pache <nico.pache@linux.dev>,
	Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
	Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] MAINTAINERS: remove myself as THP co-maintainer
Date: Thu, 27 Aug 2026 16:17:16 +0100	[thread overview]
Message-ID: <05f7cf39-b133-4cc9-8082-40b081b7f908@linux.dev> (raw)
In-Reply-To: <apBG3YnZcHhlvU3m@gremlin>



On 27/08/2026 15:25, Lorenzo Stoakes (ARM) wrote:
> On Thu, Aug 27, 2026 at 03:15:47PM +0100, Usama Arif wrote:
>>
>>
>> On 26/08/2026 12:31, 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!
>>>
>> Ah so sorry to see you step down, you made THP genuinely better!
>>
>> The numbers show the amount of effort you have put in, but they don't capture
>> how consistently useful and detailed your reviews are, with the aim of
>> always trying to make the patches and THP better!
>>
>> Thanks for being an awesome maintainer and hopefully you will consider
>> coming back soon!
> 
> Thanks Usama! :) I know we started off with some fireworks on review 😅 but
> you've always been fantastic to work with and it's been great to see you
> develop as a contributor.
> 
> BTW, I did want to say but never got around to it - I love how you've
> approached the PUD THP stuff - i.e. getting the huge swap stuff sorted
> first, gradually building things up, etc.!
> 
> You've always given interesting sessions + input at LSF and have had great
> insights on how stuff interacts with the Meta fleet also! :)
> 
> It was especially interesting to hear that 512 MiB huge pages have actually
> resulted in far less memory usage than you might expect :)
> 
> I will still be busy upstream with the 4 other maintainerships to keep me
> busy, along with series both in kvmarm and core mm so don't worry I'm not
> going anywhere :)
> 
> And as I said to David and others, always feel free to cc- me or ping me
> off-list etc. if I can be of use for THP stuff, even though I'm taking a
> break from the maintainership side!
> 

Thanks for the kind words! It has been awesome working with you and discussing
different topics at conferences and the mailing list! I am sure we will continue to
in the future!

>>
>> Thanks,
>> Usama
> 
> --
> Cheers, Lorenzo



  reply	other threads:[~2026-08-27 15:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26  9:56 [PATCH] MAINTAINERS: remove myself as THP co-maintainer 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
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 [this message]
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=05f7cf39-b133-4cc9-8082-40b081b7f908@linux.dev \
    --to=usama.arif@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=lance.yang@linux.dev \
    --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=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 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.