[PATCH 2/7] mm: introduce local state for lazy_mmu sections

[Lorenzo Stoakes]

On Fri, Sep 05, 2025 at 12:21:40PM +0100, Lorenzo Stoakes wrote:
> You should really base on mm-new.
>
> You need to account for everything that is potentially going to go
> upstream. mm-stable is generally not actually populated all too well until
> shortly before merge window anyway.

Just to note that mm-unstable is also fine. Despite its name, it's substantially
more stable than mm-new, which can even break the build and appears to have no
checks performed on it at all.

But mm-new is the most uptodate version of all the mm code.

Thanks, Lorenzo