From: Roman Gushchin <roman.gushchin@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: sashiko@lists.linux.dev, Zi Yan <ziy@nvidia.com>
Subject: Re: [PATCH v4 00/16] Remove PG_private by using page/folio->private checks instead
Date: Tue, 15 Sep 2026 23:14:03 +0000 [thread overview]
Message-ID: <7ia4mrti6rb8.fsf@castle.c.googlers.com> (raw)
In-Reply-To: <20260915144958.23000e3a625ecc24f48ee568@linux-foundation.org> (Andrew Morton's message of "Tue, 15 Sep 2026 14:49:58 -0700")
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
prev parent reply other threads:[~2026-09-15 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260913-remove-pg_private-v4-0-848550f7574e@nvidia.com>
2026-09-15 21:49 ` [PATCH v4 00/16] Remove PG_private by using page/folio->private checks instead Andrew Morton
2026-09-15 23:14 ` Roman Gushchin [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=7ia4mrti6rb8.fsf@castle.c.googlers.com \
--to=roman.gushchin@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=sashiko@lists.linux.dev \
--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