Re: [PATCH v4 00/16] Remove PG_private by using page/folio->private checks instead

[Roman Gushchin <roman.gushchin@linux.dev>]

Andrew Morton <akpm@linux-foundation.org> writes:

> Hey all,
>
> On Sun, 13 Sep 2026 22:23:58 -0400 Zi Yan <ziy@nvidia.com> wrote:
>
>> Subject: [PATCH v4 00/16] Remove PG_private by using page/folio->private checks instead
>> Date: Sun, 13 Sep 2026 22:23:58 -0400
>> Sender: owner-linux-mm@kvack.org
>> X-Mailer: b4 0.16.0
>> 
>> Hi all,
>> 
>> This patchset removes PG_private to make space for upcoming PG_folio for
>> identifying pages from a folio (more details in Note below). Instead of
>> checking PG_private, all code is changed to check page/folio->private !=
>> NULL instead.
>
> Sashiko seems to have done something wrong with this review.
>
> The original thread is at
> https://lore.kernel.org/20260913-remove-pg_private-v4-0-848550f7574e@nvidia.com
>
> its title is
>
> 	[PATCH v4 00/16] Remove PG_private by using page/folio->private checks instead
>
> its msgid is
>
> 	20260913-remove-pg_private-v4-0-848550f7574e@nvidia.com
>
>
>
> The relevant Sashiko URL is
>
> 	https://sashiko.dev/#/patchset/20260913-remove-pg_private-v4-0-848550f7574e@nvidia.com
>
>
> That URL shows the email conversation correctly.  But the page's title
> and the associated code review refer to a different patchset entirely,
> "[PATCH 1/3] md: Use folio_alloc_buffers()".
>
>
> I used the search box for "Remove PG_private by using
> page/folio->private checks instead" and got the same result.
>
>
> a) something odd happened!

Yep, I'm looking into fixing it.

>
> b) is there any way of finding the review for "[PATCH v4 00/16]
>    Remove PG_private by using page/folio->private checks instead"?

https://sashiko.dev/#/patchset/73521

Thanks