Re: [PATCH 0/6] mm: preparatory patches for PMD level swap entries

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

On Wed, 1 Jul 2026 09:04:33 +0100 Lorenzo Stoakes <ljs@kernel.org> wrote:

> On Tue, Jun 30, 2026 at 12:50:24PM -0700, Andrew Morton wrote:
> > On Tue, 30 Jun 2026 09:34:37 -0700 Usama Arif <usama.arif@linux.dev> wrote:
> >
> > > This is the preparatory part of the PMD page table swapin work.
> >
> > Thanks.
> >
> > This comes reasonably reviewed, so I'll queue it in mm-new.
> >
> > Why?
> >
> > - Human review coverage and AI review make me believe this isn't the
> >   final version at all, but I do believe this is something we want in
> >   7.2, and getting it under test early will help to push it along.
> >
> > - Getting it in there early means that others will base their work on
> >   material which will probably be upstreamed this cycle, so this gives
> >   them a more accurate base against which to work.
> >
> > Sashiko did find a lot to talk about, some of it pre-existing so can
> > people who work on this code please take a look at
> >
> > 	https://sashiko.dev/#/patchset/20260630164143.1595669-1-usama.arif@linux.dev
> >
> >
> 
> Hm, my understanding was that mm-new is where we take everything submitted for
> early testing?
> 
> Did something change?

mm-new has always been a few day front-end to mm-unstable.  To protect
linux-next from brand new material.  It serves no other purpose.

Almost.  I'll very occasionally use it for short-term not-for-upstream
playthings.

> Generally anything submitted early in the cycle is expected to land in the cycle
> unless there's significant adverse review or other reasons it can't be taken.

Yup.  Don't want anything in mm.git which isn't expected to be
upstreamed in the next merge window.

Nowadays I'm reluctant to add anything which hasn't had a decent scan
from reviewers.  If it's something I'd particularly like to get
upstreamed I'll very occasionally add it early, to help push it along.