From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
Andrew Morton <akpm@linux-foundation.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>,
Usama Arif <usama.arif@linux.dev>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] MAINTAINERS: remove myself as THP co-maintainer
Date: Wed, 26 Aug 2026 12:09:31 +0200 [thread overview]
Message-ID: <6293dc55-e69f-498c-8290-b85202db605e@kernel.org> (raw)
In-Reply-To: <20260826-drop-thp-maintainership-v1-1-3d102748fa17@kernel.org>
On 8/26/26 11:56, Lorenzo Stoakes (ARM) wrote:
> Unfortunately my workload is such that I simply no longer have the time to
> give THP the focus that it deserves.
THP is, unfortunately, one of the busiest MM components, and also the ones where
we have to deal with significant legacy code, many suboptimal past design
decisions ... and plenty of ideas for improvements that require constant
pushback to not make the situation even worse. The time spent on discussions
alone is massive.
Fortunately we have a growing list of reviewers.
It's mostly thankless work, really; but I'd like to express my sincere gratitude
for all the work you put into co-maintaing THP over (/me checks MAINTAINERS)
more than 1 year!
>
> So, at least temporarily, step down from the role.
>
I'm sorry but I can't let you go entirely ;) I'll make sure to CC you on patches
that need your feedback!
Thanks again, Lorenzo!
--
Cheers,
David
next prev parent reply other threads:[~2026-08-26 10:09 UTC|newest]
Thread overview: 3+ 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) [this message]
2026-08-26 10:23 ` 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=6293dc55-e69f-498c-8290-b85202db605e@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--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=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