From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Jinjiang Tu <tujinjiang@huawei.com>,
akpm@linux-foundation.org, ziy@nvidia.com, 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
Subject: Re: [PATCH v2 3/3] fs: stable_page_flags(): simplify KPF_IDLE handling
Date: Mon, 20 Jul 2026 10:32:06 +0100 [thread overview]
Message-ID: <85d4c9da-c89a-4c7a-8c35-31d4c185f4e9@kernel.org> (raw)
In-Reply-To: <20260720033021.4091944-4-tujinjiang@huawei.com>
On 7/20/26 04:30, Jinjiang Tu wrote:
> For KPF_IDLE, folio_test_idle() check in set_ps_flags() already handles
> all config cases, so remove the duplicate code in stable_page_flags() that
> deals with CONFIG_PAGE_IDLE_FLAG for the 64‑bit case.
>
> No functional change is intended.
>
> Signed-off-by: Jinjiang Tu <tujinjiang@huawei.com>
> ---
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
next prev parent reply other threads:[~2026-07-20 9:32 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) [this message]
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=85d4c9da-c89a-4c7a-8c35-31d4c185f4e9@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--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