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

[Lorenzo Stoakes]

+cc Mark

On Thu, Jul 02, 2026 at 04:08:03PM +0300, Mike Rapoport wrote:
> On Thu, Jul 02, 2026 at 11:48:24AM +0100, Lorenzo Stoakes wrote:
> > +cc Mike re: CI.
> >
> > On Wed, Jul 01, 2026 at 04:46:13PM -0700, Andrew Morton wrote:
> > > On Wed, 1 Jul 2026 09:04:33 +0100 Lorenzo Stoakes <ljs@xxxxxxxxxx> wrote:
...
> > > > 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.
> >
> > Well it only serves a purpose if it gives us better testing.
> >
> > We have a CI running tests now though, Mike - is that predicated on material
> > being in mm-new or does it just grab the email?
>
> CI grabs patches from patchwork and tries to apply them to one of the three
> bases: mm-unstable, mm-new or the latest Linus' commit merged into mm.git.
>
> If patches apply, the other bases are not checked.
>
> This patches applied cleanly to mm-unstable and successfully passed (at
> least once :) )
> https://github.com/linux-mm/linux-mm/actions/runs/28544575927/
>
> > If the CI is just grabbing email I wonder whether there's much purpose in the
> > mm-new branch at all.
>
> I can't say that CI I run has a great coverage. I don't know what coverage
> mm-new has though

Well we're very grateful for what coverage it has :) and that's nice to have it
work with email like that also, makes life simpler.

Mark - are you running tests based on mm-new? I'm not sure where things stand on
that?

>
> > Thanks, Lorenzo
>
> --
> Sincerely yours,
> Mike.

Thanks, Lorenzo