From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: 李佑鸿 <dayou5941@163.com>
Cc: akpm@linux-foundation.org, david@kernel.org, ziy@nvidia.com,
linux-mm@kvack.org, Li Youhong <liyouhong@kylinos.cn>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [PATCH] mm/huge_memory: add VM_WARN_ON_ONCE_FOLIO() in min_order_for_split()
Date: Thu, 6 Aug 2026 08:36:29 +0100 [thread overview]
Message-ID: <anQ5QyzLCdXxlEOE@lucifer> (raw)
In-Reply-To: <17316ab0.5714.19fd5fef275.Coremail.dayou5941@163.com>
On Thu, Aug 06, 2026 at 03:34:43PM +0800, 李佑鸿 wrote:
> Hi Lorenzo,
> Thank you for your feedback, and I apologize for that.
> You are right — I may have misunderstood what you meant by "separate patch." I thought you wanted it sent as an independent patch, but you clearly meant as part of the same series, placed after the fix patch that makes the warning meaningful.
> I'll resend the full series as a single patchset (v5 1/2 + 2/2):
>
> Patch 1: mm/memory-failure: fix folio refcount leak and locking in
> soft/hard offline
> Patch 2: mm/huge_memory: add VM_WARN_ON_ONCE_FOLIO() in
> min_order_for_split()
>
> The second patch depends on the first, so they must go together as
> you originally requested.
> I'll send this out by tomorrow as you asked. My apologies for the
> noise and the wasted review time.
No I think it's better that we handle this patch, please don't send any more
revisions.
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-08-06 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 3:21 [PATCH] mm/huge_memory: add VM_WARN_ON_ONCE_FOLIO() in min_order_for_split() dayou5941
2026-08-06 6:32 ` Lorenzo Stoakes (ARM)
2026-08-06 7:34 ` 李佑鸿
2026-08-06 7:36 ` Lorenzo Stoakes (ARM) [this message]
2026-08-06 11:15 ` David Hildenbrand (Arm)
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=anQ5QyzLCdXxlEOE@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=dayou5941@163.com \
--cc=linux-mm@kvack.org \
--cc=liyouhong@kylinos.cn \
--cc=lorenzo.stoakes@oracle.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.