From: Andrew Morton <akpm@linux-foundation.org>
To: Muchun Song <muchun.song@linux.dev>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Muchun Song <songmuchun@bytedance.com>,
Oscar Salvador <osalvador@suse.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
aneesh.kumar@linux.ibm.com, joao.m.martins@oracle.com,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 v5 4/6] mm/sparse-vmemmap: Fix DAX vmemmap accounting with optimization
Date: Thu, 23 Apr 2026 06:14:02 -0700 [thread overview]
Message-ID: <20260423061402.71f0f37285e922f28853e5f8@linux-foundation.org> (raw)
In-Reply-To: <D642D89B-CC3C-46A0-B1D6-3DC2C4DDB874@linux.dev>
On Thu, 23 Apr 2026 20:43:02 +0800 Muchun Song <muchun.song@linux.dev> wrote:
> >
> > Ideally, split the series up into one series for 7.1-rcX+stable, another
> > series for 7.2.rc1.
>
> Given that these issues have existed for a long time and the trigger
> frequency is very low, I suggest we take a more conservative timing.
>
> We can prioritize getting the series into 7.2-rc1 first. Once they have
> 'baked' in the mainline for a while without issues, we can then proceed
> with the backport to -stable (7.1.x). This avoids rushing risky changes
> into stable branches.
Good plan. thanks.
next prev parent reply other threads:[~2026-04-23 13:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 7:19 [PATCH v5 0/6] mm: fix vmemmap optimization accounting and initialization Muchun Song
2026-04-23 7:19 ` [PATCH v5 v5 1/6] mm/sparse-vmemmap: Fix vmemmap accounting underflow Muchun Song
2026-04-23 7:19 ` [PATCH v5 v5 2/6] mm/memory_hotplug: Fix incorrect altmap passing in error path Muchun Song
2026-04-23 10:38 ` David Hildenbrand (Arm)
2026-04-23 12:18 ` Muchun Song
2026-04-23 12:28 ` David Hildenbrand (Arm)
2026-04-23 12:31 ` Muchun Song
2026-04-23 7:19 ` [PATCH v5 v5 3/6] mm/sparse-vmemmap: Pass @pgmap argument to memory deactivation paths Muchun Song
2026-04-23 7:19 ` [PATCH v5 v5 4/6] mm/sparse-vmemmap: Fix DAX vmemmap accounting with optimization Muchun Song
2026-04-23 10:40 ` David Hildenbrand (Arm)
2026-04-23 12:04 ` Muchun Song
2026-04-23 12:32 ` Andrew Morton
2026-04-23 12:43 ` Muchun Song
2026-04-23 13:14 ` Andrew Morton [this message]
2026-04-23 7:19 ` [PATCH v5 v5 5/6] mm/mm_init: Fix pageblock migratetype for ZONE_DEVICE compound pages Muchun Song
2026-04-23 10:41 ` David Hildenbrand (Arm)
2026-04-23 7:19 ` [PATCH v5 v5 6/6] mm/mm_init: Fix uninitialized struct pages for ZONE_DEVICE Muchun Song
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=20260423061402.71f0f37285e922f28853e5f8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=david@kernel.org \
--cc=joao.m.martins@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ljs@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mhocko@suse.com \
--cc=mpe@ellerman.id.au \
--cc=muchun.song@linux.dev \
--cc=npiggin@gmail.com \
--cc=osalvador@suse.de \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/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