Linux filesystem development
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jinjiang Tu <tujinjiang@huawei.com>
Cc: <ziy@nvidia.com>, <david@kernel.org>, <luizcap@redhat.com>,
	<willy@infradead.org>, <linmiaohe@huawei.com>,
	<svetly.todorov@memverge.com>, <xu.xin16@zte.com.cn>,
	<chengming.zhou@linux.dev>, <linux-fsdevel@vger.kernel.org>,
	<linux-mm@kvack.org>, <wangkefeng.wang@huawei.com>,
	<sunnanyong@huawei.com>, Luiz Capitulino <luizcap@redhat.com>
Subject: Re: [PATCH v2 0/3] cleanup for stable_page_flags()
Date: Sun, 19 Jul 2026 22:30:10 -0700	[thread overview]
Message-ID: <20260719223010.dc6851665fb226c73948c69e@linux-foundation.org> (raw)
In-Reply-To: <20260720033021.4091944-1-tujinjiang@huawei.com>

On Mon, 20 Jul 2026 11:30:18 +0800 Jinjiang Tu <tujinjiang@huawei.com> wrote:

> This series cleans up stable_page_flags(), see the details in the commit
> message.

Thanks, I'll await further review input on this series.

AI review might have found a couple of pre-existing issues.  Arguably
both are around the page-snapshotting code:
	https://sashiko.dev/#/patchset/20260720033021.4091944-1-tujinjiang@huawei.com

      parent reply	other threads:[~2026-07-20  5:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  3:30 [PATCH v2 0/3] cleanup for stable_page_flags() Jinjiang Tu
2026-07-20  3:30 ` [PATCH v2 1/3] fs: stable_page_flags(): use BIT_ULL() for KPF flags Jinjiang Tu
2026-07-20  3:30 ` [PATCH v2 2/3] fs: stable_page_flags(): use folio_test_*() helpers Jinjiang Tu
2026-07-20  9:30   ` David Hildenbrand (Arm)
2026-07-20  3:30 ` [PATCH v2 3/3] fs: stable_page_flags(): simplify KPF_IDLE handling Jinjiang Tu
2026-07-20  9:32   ` David Hildenbrand (Arm)
2026-07-20  5:30 ` Andrew Morton [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=20260719223010.dc6851665fb226c73948c69e@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=chengming.zhou@linux.dev \
    --cc=david@kernel.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luizcap@redhat.com \
    --cc=sunnanyong@huawei.com \
    --cc=svetly.todorov@memverge.com \
    --cc=tujinjiang@huawei.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.org \
    --cc=xu.xin16@zte.com.cn \
    --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