From: Kaitao Cheng <kaitao.cheng@linux.dev>
To: "Oscar Salvador (SUSE)" <osalvador@kernel.org>,
David Hildenbrand <david@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Dan Williams <djbw@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Ira Weiny <iweiny@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
linux-mm@kvack.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org,
Kaitao Cheng <chengkaitao@kylinos.cn>
Subject: Re: [PATCH 2/2] nvdimm/pmem: Remove test_and_clear_pmem_poison()
Date: Tue, 22 Sep 2026 12:44:19 +0800 [thread overview]
Message-ID: <10159c57-091e-474a-a154-4f675a39dcc2@linux.dev> (raw)
In-Reply-To: <arIBvO3cFQ53ivG3@localhost.localdomain>
在 2026/9/22 12:19, Oscar Salvador (SUSE) 写道:
> On Thu, Sep 03, 2026 at 01:35:35PM +0800, Kaitao Cheng wrote:
>> From: Kaitao Cheng <chengkaitao@kylinos.cn>
>>
>> TestClearPageHWPoison() is now defined regardless of whether
>> CONFIG_MEMORY_FAILURE is enabled, returning false when memory failure
>> handling is unavailable.
>>
>> The test_and_clear_pmem_poison() wrapper duplicates this configuration
>> handling and has no other pmem-specific behavior.
>>
>> Call TestClearPageHWPoison() directly and remove the redundant wrapper.
>> This also removes the need to include page-flags.h from pmem.h.
>>
>> No functional change is intended.
>>
>> Signed-off-by: Kaitao Cheng <chengkaitao@kylinos.cn>
>
> Nice cleanup, but as David noted, please squash patch#1 into this one.
Although NVDIMM is currently the only external user of TestClearPageHWPoison,
I still consider it a generic declaration. Combining the two patches might
give the impression that TestClearPageHWPoison exists solely to serve a
specific driver.
That said, I’m not opposed to merging the two patches, as doing so would
make the submission more concise.
I think both approaches have their own advantages and disadvantages,
which is why I haven’t sent a v2 yet.
> Reviewed-by: Oscar Salvador <osalvador@suse.de>
>
>
--
Thanks
Kaitao Cheng
next prev parent reply other threads:[~2026-09-22 4:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 5:35 [PATCH 0/2] Make HWPoison helpers config-independent Kaitao Cheng
2026-09-03 5:35 ` [PATCH 1/2] mm/page-flags: Define HWPoison test-and-change helpers unconditionally Kaitao Cheng
2026-09-03 6:15 ` Muchun Song
2026-09-07 15:42 ` David Hildenbrand (Arm)
2026-09-26 6:19 ` Andrew Morton
2026-09-26 7:06 ` Kaitao Cheng
2026-09-03 5:35 ` [PATCH 2/2] nvdimm/pmem: Remove test_and_clear_pmem_poison() Kaitao Cheng
2026-09-03 6:17 ` Muchun Song
2026-09-07 15:42 ` David Hildenbrand (Arm)
2026-09-22 4:19 ` Oscar Salvador (SUSE)
2026-09-22 4:44 ` Kaitao Cheng [this message]
2026-09-22 13:57 ` David Hildenbrand (Arm)
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=10159c57-091e-474a-a154-4f675a39dcc2@linux.dev \
--to=kaitao.cheng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=chengkaitao@kylinos.cn \
--cc=dave.jiang@intel.com \
--cc=david@kernel.org \
--cc=djbw@kernel.org \
--cc=iweiny@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=nvdimm@lists.linux.dev \
--cc=osalvador@kernel.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=vishal.l.verma@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.