From: Jinjiang Tu <tujinjiang@huawei.com>
To: <akpm@linux-foundation.org>, <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>
Cc: <wangkefeng.wang@huawei.com>, <sunnanyong@huawei.com>,
<tujinjiang@huawei.com>
Subject: [PATCH v2 0/3] cleanup for stable_page_flags()
Date: Mon, 20 Jul 2026 11:30:18 +0800 [thread overview]
Message-ID: <20260720033021.4091944-1-tujinjiang@huawei.com> (raw)
This series cleans up stable_page_flags(), see the details in the commit
message.
Changes since v1:
* add missing "1 << KPF_*" covertions for patch 1
* collect Acked-by for patch 1
* only convert folio-specific flags to folio_test_*() helpers
* move KPF_IDLE cleanup to a separate patch
Jinjiang Tu (3):
fs: stable_page_flags(): use BIT_ULL() for KPF flags
fs: stable_page_flags(): use folio_test_*() helpers
fs: stable_page_flags(): simplify KPF_IDLE handling
fs/proc/page.c | 56 +++++++++++++++++++++-----------------------------
1 file changed, 23 insertions(+), 33 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-20 3:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 3:30 Jinjiang Tu [this message]
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 ` [PATCH v2 0/3] cleanup for stable_page_flags() Andrew Morton
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=20260720033021.4091944-1-tujinjiang@huawei.com \
--to=tujinjiang@huawei.com \
--cc=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=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