From: Krzysztof Kozlowski <krzk@kernel.org>
To: Josh Law <joshlaw48@gmail.com>,
"David Hildenbrand (Arm)" <david@kernel.org>,
akpm@linux-foundation.org
Cc: linux-mm@kvack.org
Subject: Re: [LSF/MM/BPF TOPIC] MM transition
Date: Thu, 23 Apr 2026 08:15:57 +0200 [thread overview]
Message-ID: <499d2411-72b5-4bc3-8db7-5a29f9fb3f20@kernel.org> (raw)
In-Reply-To: <4B3D556A-AEA8-4143-85EA-CEB76801B879@gmail.com>
On 22/04/2026 20:48, Josh Law wrote:
> [Snip! :)]
>
>>
>> Yes, but he also writes (nonmm) "it's pretty quiet" ;)
>>
>> So, MM is the real struggle.
>>
>>> so the (basically) orphaned files like glob, or smth like that,
>>> could go to someone who understands the code better and more likely than
>>> not, has time to review.
>>>
>>> We may have to have a think about this.
>>
>> I'm sure
>>
>> (a) Andrew will enjoy being around and we will enjoy having Andrew around.
>> (b) If Andrews workload is still too high, even after MM is handled
>> differently,
>> or when he wants to completely retire, I'm sure he will speak up.
>>
>> One step at a time.
>>
>>
>
> Agreed. If he needs help reviewing patches in lib, he can feel free to
> CC: me, best I can do showing he helped me when I first started :)
NAK, you violated our trust and you should not be close to anything
related to MM or lib.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-23 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 16:42 Andrew Morton
2026-04-21 19:25 ` Josh Law
2026-04-22 18:18 ` David Hildenbrand (Arm)
2026-04-22 18:22 ` Josh Law
2026-04-22 18:44 ` David Hildenbrand (Arm)
2026-04-22 18:48 ` Josh Law
2026-04-23 6:15 ` Krzysztof Kozlowski [this message]
2026-04-22 19:03 ` Matthew Wilcox
2026-04-22 19:13 ` Josh Law
2026-04-23 6:18 ` Krzysztof Kozlowski
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=499d2411-72b5-4bc3-8db7-5a29f9fb3f20@kernel.org \
--to=krzk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=joshlaw48@gmail.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox