Re: MM: Firefighting mode

[Andrew Morton <akpm@linux-foundation.org>]

On Mon, 9 Nov 2026 19:15:17 +0100 "David Hildenbrand (Arm)" <david@kernel.org> wrote:

> Hi all,
> 
>   "Your message is important to us, please continue to hold. An MM expert will
>    be with you as soon as possible."

<ptsd triggered>

Thanks, David.

> I wanted to send this out last week, but somehow didn't manage to do it even
> after being reminded by Lorenzo (thanks!) :)
> 
> If you haven't noticed, the MM team is busy right now either fixing bugs or
> reviewing these fixes.
> 
> Or fixing bugs we found while reviewing fixes.
> 
> Or reviewing fixes for bugs we found while reviewing fixes.
> 
> Or ...
> 
> Anyhow, our focus this cycle in MM is clearly on bugfixes of different urgency,
> and I'd like to thank all of our MM community members for helping out with
> fixing bugs or reviewing fixes!

And can I draw attention to a thing Lorenzo said recently:
	https://lore.kernel.org/arOMefPN1gxMpyx8@gremlin

As I mentioned at this year's LSFMMBPF meeting, it continues to be the
case that our review activity is quite lopsided.

So yes, people, please do dig in and help.

> That doesn't mean that we should stop any other development. In particular, I
> want us to continue making progress on work we started in the last cycle.
> 
> Removing code or nice (easy-to-review) cleanups are always appreciated.
> 
> But be aware that we only have limited capacity for big, very complicated, or
> controversial things that need a lot of attention from MM maintainers and
> reviewers. In particular if it is low priority.
> 
> So, some stuff will have to wait ... longer than usual.
> 
> So if you feel ignored, it's just the MM team being busy fighting fires.

But never forgotten.  I'm tracking a backlog of ~150 series/singletons
spanning from Oct 10 to present.  I won't let stuff fall through
cracks, but delays are to be expected!