From: Andrew Morton <akpm@linux-foundation.org>
To: <ankita@nvidia.com>
Cc: <aniketa@nvidia.com>, <vsethi@nvidia.com>, <jgg@nvidia.com>,
<mochs@nvidia.com>, <skolothumtho@nvidia.com>,
<linmiaohe@huawei.com>, <nao.horiguchi@gmail.com>,
<david@redhat.com>, <lorenzo.stoakes@oracle.com>,
<Liam.Howlett@oracle.com>, <vbabka@suse.cz>, <rppt@kernel.org>,
<surenb@google.com>, <mhocko@suse.com>, <tony.luck@intel.com>,
<bp@alien8.de>, <rafael@kernel.org>, <guohanjun@huawei.com>,
<mchehab@kernel.org>, <lenb@kernel.org>, <kevin.tian@intel.com>,
<alex@shazbot.org>, <cjia@nvidia.com>, <kwankhede@nvidia.com>,
<targupta@nvidia.com>, <zhiw@nvidia.com>, <dnigam@nvidia.com>,
<kjaju@nvidia.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-edac@vger.kernel.org>,
<Jonathan.Cameron@huawei.com>, <ira.weiny@intel.com>,
<Smita.KoralahalliChannabasappa@amd.com>,
<u.kleine-koenig@baylibre.com>, <peterz@infradead.org>,
<linux-acpi@vger.kernel.org>, <kvm@vger.kernel.org>
Subject: Re: [PATCH v5 2/3] mm: handle poisoning of pfn without struct pages
Date: Mon, 3 Nov 2025 18:49:31 -0800 [thread overview]
Message-ID: <20251103184931.5a8e0be8f959ba2a0b6b814b@linux-foundation.org> (raw)
In-Reply-To: <20251102184434.2406-3-ankita@nvidia.com>
On Sun, 2 Nov 2025 18:44:33 +0000 <ankita@nvidia.com> wrote:
> diff --git a/include/linux/memory-failure.h b/include/linux/memory-failure.h
> new file mode 100644
OK. I assume there is a bunch of memory-failure material which can now
be moved into the new memory-failure.h.
next prev parent reply other threads:[~2025-11-04 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 18:44 [PATCH v5 0/3] mm: Implement ECC handling for pfn with no struct page ankita
2025-11-02 18:44 ` [PATCH v5 1/3] mm: Change ghes code to allow poison of non-struct pfn ankita
2025-11-02 18:44 ` [PATCH v5 2/3] mm: handle poisoning of pfn without struct pages ankita
2025-11-04 2:49 ` Andrew Morton [this message]
2025-11-02 18:44 ` [PATCH v5 3/3] vfio/nvgrace-gpu: register device memory for poison handling ankita
2025-11-06 21:56 ` Alex Williamson
2025-11-04 2:47 ` [PATCH v5 0/3] mm: Implement ECC handling for pfn with no struct page Andrew Morton
2025-11-04 17:15 ` Ankit Agrawal
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=20251103184931.5a8e0be8f959ba2a0b6b814b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=Liam.Howlett@oracle.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=alex@shazbot.org \
--cc=aniketa@nvidia.com \
--cc=ankita@nvidia.com \
--cc=bp@alien8.de \
--cc=cjia@nvidia.com \
--cc=david@redhat.com \
--cc=dnigam@nvidia.com \
--cc=guohanjun@huawei.com \
--cc=ira.weiny@intel.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kjaju@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=lenb@kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mchehab@kernel.org \
--cc=mhocko@suse.com \
--cc=mochs@nvidia.com \
--cc=nao.horiguchi@gmail.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rppt@kernel.org \
--cc=skolothumtho@nvidia.com \
--cc=surenb@google.com \
--cc=targupta@nvidia.com \
--cc=tony.luck@intel.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vbabka@suse.cz \
--cc=vsethi@nvidia.com \
--cc=zhiw@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