Re: [PATCH v2] mm/page_alloc: drop flag-conversion "optimisation"

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

On Fri, 19 Jun 2026 16:53:41 +0200 "David Hildenbrand (Arm)" <david@kernel.org> wrote:

> On 6/19/26 14:34, Brendan Jackman wrote:
> > On Fri Jun 19, 2026 at 12:27 PM UTC, Zi Yan wrote:
> >> On Fri Jun 19, 2026 at 7:53 AM EDT, Brendan Jackman wrote:
> >>>
> >>> Hi Andrew,
> >>>
> >>> This one didn't make it into any of the latest mm-* branches, is
> >>> anything blocked here?
> >>
> >> It is in the quiet period, no patch will be picked up until -rc1 is
> >> out. If yours is not picked up then, feel free to resend it.
> > 
> > Ah, I thought mm-unstable didn't care about merge windows. It got
> > updated 2 days ago, but now I realise that's probably just coz Andrew
> > was updating mm-stable and then rebased onto it?
> > 
> > Thanks for clarifying.
> 
> We're targeting for mm-unstable to only have material that is already upstream
> at the end of the merge window.

What they all said ;)

Officially (and for good reasons) we aren't supposed to add new
material to linux-next until -rc1 is released.

mm.git has the mm-new branch which isn't included in linux-next so
after MM is all merged up I start working through the backlog which I
accumulated during quiet-time and merging some of it into mm-new.

Backlog was ~1700 emails this time.  Most of which gets skipped for
various reasons,

This particular patch looks nice to me.  Code is cleaner and the change
reduces page_alloc.o's .text (x86_64 defconfig) from 46571 to 46443,
which is a good sign.  So I'll add it, along with a "needs more review"
note.

Thanks.