From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Zi Yan <ziy@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Wei Yang <richard.weiyang@gmail.com>,
linmiaohe@huawei.com, david@redhat.com, jane.chu@oracle.com,
kernel@pankajraghav.com,
syzbot+e6367ea2fdab6ed46056@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, mcgrof@kernel.org,
nao.horiguchi@gmail.com,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH v2 1/3] mm/huge_memory: do not change split_huge_page*() target order silently.
Date: Fri, 17 Oct 2025 10:06:41 +0100 [thread overview]
Message-ID: <16b10383-1d3a-428c-918a-3bbf1f9f495d@lucifer.local> (raw)
In-Reply-To: <E88B5579-DE01-4F33-B666-CC29F32EEF70@nvidia.com>
On Thu, Oct 16, 2025 at 09:03:27PM -0400, Zi Yan wrote:
> On 16 Oct 2025, at 16:59, Andrew Morton wrote:
>
> > On Thu, 16 Oct 2025 10:32:17 -0400 Zi Yan <ziy@nvidia.com> wrote:
> >
> >>> Do we want to cc stable?
> >>
> >> This only triggers a warning, so I am inclined not to.
> >> But some config decides to crash on kernel warnings. If anyone thinks
> >> it is worth ccing stable, please let me know.
> >
> > Yes please. Kernel warnings are pretty serious and I do like to fix
> > them in -stable when possible.
> >
> > That means this patch will have a different routing and priority than
> > the other two so please split the warning fix out from the series.
>
> OK. Let me send this one and cc stable.
You've added a bunch of confusion here, now if I review the rest of this series
it looks like I'm reviewing it with this stale patch included.
Can you please resend the remainder of the series as a v3 so it's clear? Thanks!
next prev parent reply other threads:[~2025-10-17 9:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 3:34 [PATCH v2 0/3] Do not change split folio target order Zi Yan
2025-10-16 3:34 ` [PATCH v2 1/3] mm/huge_memory: do not change split_huge_page*() target order silently Zi Yan
2025-10-16 7:31 ` Wei Yang
2025-10-16 14:32 ` Zi Yan
2025-10-16 20:59 ` Andrew Morton
2025-10-17 1:03 ` Zi Yan
2025-10-17 9:06 ` Lorenzo Stoakes [this message]
2025-10-17 9:10 ` Lorenzo Stoakes
2025-10-17 14:16 ` Zi Yan
2025-10-17 14:32 ` Lorenzo Stoakes
2025-10-18 0:05 ` Andrew Morton
2025-10-17 1:01 ` Wei Yang
2025-10-16 3:34 ` [PATCH v2 2/3] mm/memory-failure: improve large block size folio handling Zi Yan
2025-10-17 9:33 ` Lorenzo Stoakes
2025-10-20 20:09 ` Zi Yan
2025-10-17 19:11 ` Yang Shi
2025-10-20 19:46 ` Zi Yan
2025-10-20 23:41 ` Yang Shi
2025-10-21 1:23 ` Zi Yan
2025-10-21 15:44 ` David Hildenbrand
2025-10-21 15:55 ` Zi Yan
2025-10-21 18:28 ` David Hildenbrand
2025-10-21 18:57 ` Zi Yan
2025-10-21 19:07 ` Yang Shi
2025-10-22 6:39 ` Miaohe Lin
2025-10-16 3:34 ` [PATCH v2 3/3] mm/huge_memory: fix kernel-doc comments for folio_split() and related Zi Yan
2025-10-17 9:20 ` Lorenzo Stoakes
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=16b10383-1d3a-428c-918a-3bbf1f9f495d@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=jane.chu@oracle.com \
--cc=kernel@pankajraghav.com \
--cc=lance.yang@linux.dev \
--cc=linmiaohe@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=nao.horiguchi@gmail.com \
--cc=npache@redhat.com \
--cc=p.raghav@samsung.com \
--cc=richard.weiyang@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=syzbot+e6367ea2fdab6ed46056@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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