From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Brendan Jackman <brendan.jackman@linux.dev>,
Zi Yan <ziy@nvidia.com>, Brendan Jackman <jackmanb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>
Cc: "Harry Yoo (Oracle)" <harry@kernel.org>,
Gregory Price <gourry@gourry.net>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/page_alloc: drop flag-conversion "optimisation"
Date: Fri, 19 Jun 2026 16:53:41 +0200 [thread overview]
Message-ID: <fbe1e70b-2a33-4db0-b390-3841c1a84522@kernel.org> (raw)
In-Reply-To: <DJD12YR8S99G.1I43PSHB77TA2@linux.dev>
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.
--
Cheers,
David
prev parent reply other threads:[~2026-06-19 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 10:54 [PATCH v2] mm/page_alloc: drop flag-conversion "optimisation" Brendan Jackman
2026-06-15 10:59 ` Brendan Jackman
2026-06-19 11:53 ` Brendan Jackman
2026-06-19 12:27 ` Zi Yan
2026-06-19 12:34 ` Brendan Jackman
2026-06-19 14:53 ` David Hildenbrand (Arm) [this message]
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=fbe1e70b-2a33-4db0-b390-3841c1a84522@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.jackman@linux.dev \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=harry@kernel.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ziy@nvidia.com \
/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