From: "Oscar Salvador (SUSE)" <osalvador@kernel.org>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: Jiaqi Yan <jiaqiyan@google.com>, Vlastimil Babka <vbabka@suse.cz>,
nao.horiguchi@gmail.com, william.roche@oracle.com,
tony.luck@intel.com, wangkefeng.wang@huawei.com,
jane.chu@oracle.com, akpm@linux-foundation.org,
osalvador@suse.de, muchun.song@linux.dev, rientjes@google.com,
duenwen@google.com, jthoughton@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Liam.Howlett@oracle.com,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
boudewijn@delta-utec.com, ziy@nvidia.com, harry.yoo@oracle.com,
willy@infradead.org, linmiaohe@huawei.com, hannes@cmpxchg.org,
jackmanb@google.com
Subject: Re: [PATCH v4 0/3] Only free healthy pages in high-order has_hwpoisoned folio
Date: Tue, 26 May 2026 19:17:44 +0200 [thread overview]
Message-ID: <ahXVuBoNUeEvLRrb@localhost.localdomain> (raw)
In-Reply-To: <ahXFPh-a_Zt1Q_r_@lucifer>
On Tue, May 26, 2026 at 05:09:28PM +0100, Lorenzo Stoakes wrote:
> On Mon, Feb 23, 2026 at 03:17:57PM -0800, Jiaqi Yan wrote:
> > Hi Vlastimil,
> >
> > Could you and other page_alloc.c reviewers share your thoughts on this
> > patchset? Thanks!
>
> Hi Jiaqi,
>
> I guess you are blocked on review here, did you intend to return to this?
>
> I'd suggest attempted a respin to get some movement here as clearly this slipped
> through the gaps last cycle.
This fell off my radar, I plan to have a look this week/early next week.
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2026-05-26 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 19:41 [PATCH v4 0/3] Only free healthy pages in high-order has_hwpoisoned folio Jiaqi Yan
2026-02-02 19:41 ` [PATCH v4 1/3] mm/page_alloc: only " Jiaqi Yan
2026-02-02 19:41 ` [PATCH v4 2/3] mm/memory-failure: set has_hwpoisoned flags on dissolved HugeTLB folio Jiaqi Yan
2026-02-02 19:41 ` [PATCH v4 3/3] mm/memory-failure: skip take_page_off_buddy after dissolving HWPoison HugeTLB page Jiaqi Yan
2026-02-04 15:23 ` [PATCH v4 0/3] Only free healthy pages in high-order has_hwpoisoned folio Boudewijn van der Heide
2026-02-04 15:48 ` Zi Yan
2026-02-06 16:16 ` Boudewijn van der Heide
2026-02-23 23:17 ` Jiaqi Yan
2026-05-26 16:09 ` Lorenzo Stoakes
2026-05-26 17:17 ` Oscar Salvador (SUSE) [this message]
2026-05-27 5:00 ` Jiaqi Yan
2026-05-27 6:36 ` Lorenzo Stoakes
2026-05-28 4:29 ` Jiaqi Yan
2026-05-28 6:23 ` 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=ahXVuBoNUeEvLRrb@localhost.localdomain \
--to=osalvador@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=boudewijn@delta-utec.com \
--cc=duenwen@google.com \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=jackmanb@google.com \
--cc=jane.chu@oracle.com \
--cc=jiaqiyan@google.com \
--cc=jthoughton@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tony.luck@intel.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=william.roche@oracle.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 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.