Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: MM: Firefighting mode
Date: Mon, 9 Nov 2026 19:15:17 +0100	[thread overview]
Message-ID: <a2f584f6-e382-4876-aa6d-d5a34de6ee59@kernel.org> (raw)

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



             reply	other threads:[~2026-11-09 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 18:15 David Hildenbrand (Arm) [this message]
2026-11-09 18:35 ` MM: Firefighting mode Andrew Morton

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=a2f584f6-e382-4876-aa6d-d5a34de6ee59@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --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