From: Andrew Morton <akpm@linux-foundation.org>
To: Zi Yan <ziy@nvidia.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
david@kernel.org, lorenzo.stoakes@oracle.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, linux-mm@kvack.org
Subject: Re: [Patch v3 2/2] mm/huge_memory: merge uniform_split_supported() and non_uniform_split_supported()
Date: Fri, 21 Nov 2025 11:15:57 -0800 [thread overview]
Message-ID: <20251121111557.78c60ba96f6478f08226d34c@linux-foundation.org> (raw)
In-Reply-To: <031D24A1-5E0E-4A34-8333-4DBA31987784@nvidia.com>
On Fri, 21 Nov 2025 14:09:39 -0500 Zi Yan <ziy@nvidia.com> wrote:
> >> Wei’s further cleanup patch can come after my refactoring by just moving
> >> a code hunk above.
> >>
> >
> > This is coming down to the wire. I'm considering dropping
> >
> > mm-huge_memory-introduce-enum-split_type-for-clarity.patch
> > mm-huge_memory-introduce-enum-split_type-for-clarity-fix.patch
> > mm-huge_memory-merge-uniform_split_supported-and-non_uniform_split_supported.patch
> >
> > and
> >
> > mm-huge_memoryc-introduce-folio_split_unmapped.patch
> > mm-huge_memoryc-introduce-folio_split_unmapped-v2.patch
> > mm-huge_memoryc-introduce-folio_split_unmapped-v2-fix.patch
> > mm-huge_memoryc-introduce-folio_split_unmapped-v2-fix-fix.patch
> >
> > and we can revisit after the upcoming merge window. Thoughts?
>
> These patches are fine as is.
Well that's good news.
> The patch I asked Wei to hold on sending
> is “[PATCH] mm/huge_memory: consolidate order-related checks into
> folio_split_supported()”[1]. The current mm-new, mm-unstable trees
> look good to me. Sorry if it was not clear.
>
>
> [1] https://lore.kernel.org/linux-mm/20251114075703.10434-1-richard.weiyang@gmail.com/
OK.
prev parent reply other threads:[~2025-11-21 19:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 3:41 [Patch v3 0/2] mm/huge_memory: Define split_type and consolidate split support checks Wei Yang
2025-11-06 3:41 ` [Patch v3 1/2] mm/huge_memory: introduce enum split_type for clarity Wei Yang
2025-11-06 10:17 ` David Hildenbrand (Red Hat)
2025-11-06 14:57 ` Wei Yang
2025-11-07 0:44 ` Zi Yan
2025-11-06 3:41 ` [Patch v3 2/2] mm/huge_memory: merge uniform_split_supported() and non_uniform_split_supported() Wei Yang
2025-11-06 10:20 ` David Hildenbrand (Red Hat)
2025-11-07 0:46 ` Zi Yan
2025-11-07 1:17 ` Wei Yang
2025-11-07 2:07 ` Zi Yan
2025-11-07 2:49 ` Wei Yang
2025-11-07 3:21 ` Zi Yan
2025-11-07 7:29 ` Wei Yang
2025-11-14 3:03 ` Wei Yang
2025-11-17 1:22 ` Wei Yang
2025-11-17 15:56 ` Zi Yan
2025-11-18 2:10 ` Wei Yang
2025-11-18 3:33 ` Wei Yang
2025-11-18 4:10 ` Zi Yan
2025-11-18 18:32 ` Andrew Morton
2025-11-18 18:55 ` Zi Yan
2025-11-18 22:06 ` Andrew Morton
2025-11-19 0:52 ` Wei Yang
2025-11-20 21:16 ` Andrew Morton
2025-11-21 0:55 ` Zi Yan
2025-11-21 9:00 ` Wei Yang
2025-11-21 14:59 ` Zi Yan
2025-11-21 16:50 ` Andrew Morton
2025-11-21 17:00 ` Zi Yan
2025-11-21 18:39 ` Andrew Morton
2025-11-21 19:09 ` Zi Yan
2025-11-21 19:15 ` Andrew Morton [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=20251121111557.78c60ba96f6478f08226d34c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=richard.weiyang@gmail.com \
--cc=ryan.roberts@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.