* MM: Firefighting mode
@ 2026-11-09 18:15 David Hildenbrand (Arm)
2026-11-09 18:35 ` Andrew Morton
0 siblings, 1 reply; 2+ messages in thread
From: David Hildenbrand (Arm) @ 2026-11-09 18:15 UTC (permalink / raw)
To: linux-mm@kvack.org; +Cc: Andrew Morton
Hi all,
"Your message is important to us, please continue to hold. An MM expert will
be with you as soon as possible."
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!
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.
--
Cheers,
David
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: MM: Firefighting mode
2026-11-09 18:15 MM: Firefighting mode David Hildenbrand (Arm)
@ 2026-11-09 18:35 ` Andrew Morton
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Morton @ 2026-11-09 18:35 UTC (permalink / raw)
To: David Hildenbrand (Arm); +Cc: linux-mm@kvack.org, Lorenzo Stoakes
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!
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-11-09 18:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-09 18:15 MM: Firefighting mode David Hildenbrand (Arm)
2026-11-09 18:35 ` Andrew Morton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox