From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: <shiju.jose@huawei.com>
Cc: <linux-edac@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<rafael@kernel.org>, <bp@alien8.de>, <tony.luck@intel.com>,
<lenb@kernel.org>, <mchehab@kernel.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <linux-cxl@vger.kernel.org>,
<j.williams@intel.com>, <dave@stgolabs.net>,
<dave.jiang@intel.com>, <alison.schofield@intel.com>,
<vishal.l.verma@intel.com>, <ira.weiny@intel.com>,
<david@redhat.com>, <Vilas.Sridharan@amd.com>,
<leo.duran@amd.com>, <Yazen.Ghannam@amd.com>,
<rientjes@google.com>, <jiaqiyan@google.com>, <Jon.Grimm@amd.com>,
<dave.hansen@linux.intel.com>, <naoya.horiguchi@nec.com>,
<james.morse@arm.com>, <jthoughton@google.com>,
<somasundaram.a@hpe.com>, <erdemaktas@google.com>,
<pgonda@google.com>, <duenwen@google.com>, <gthelen@google.com>,
<wschwartz@amperecomputing.com>, <dferguson@amperecomputing.com>,
<wbs@os.amperecomputing.com>, <nifan.cxl@gmail.com>,
<tanxiaofei@huawei.com>, <prime.zeng@hisilicon.com>,
<roberto.sassu@huawei.com>, <kangkang.shen@futurewei.com>,
<wanghuiqiang@huawei.com>, <linuxarm@huawei.com>
Subject: Re: [PATCH linux-next 0/2] ACPI: Add support for ACPI RAS2 feature table
Date: Mon, 3 Mar 2025 17:35:38 +0800 [thread overview]
Message-ID: <20250303173538.000007cd@huawei.com> (raw)
In-Reply-To: <20250228122752.2062-1-shiju.jose@huawei.com>
On Fri, 28 Feb 2025 12:27:48 +0000
<shiju.jose@huawei.com> wrote:
> From: Shiju Jose <shiju.jose@huawei.com>
>
> Add support for ACPI RAS2 feature table (RAS2) defined in the ACPI 6.5
> specification, section 5.2.21 and RAS2 HW based memory scrubbing feature.
>
> ACPI RAS2 patches were part of the EDAC series [1].
Whilst linux-next now contains the EDAC patches, we shouldn't base
a feature submission on it. This should be the same as you
did for the CXL tree with a statement that it depends on
https://web.git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git/log/?h=edac-cxl
which is the immutable tag / branch Borislav provided.
I doubt there is anything else hitting this code so
shouldn't be any need to rebase (I could be wrong though!)
Assuming everyone is happy with this series, who is going to pick
it up?
Borislav via ras.git, or Rafael via acpi.git? I don't really
have any preference other than making sure it doesn't fall down
the cracks!
Jonathan
>
> 1. https://lore.kernel.org/linux-cxl/20250212143654.1893-1-shiju.jose@huawei.com/
>
> Shiju Jose (2):
> ACPI:RAS2: Add ACPI RAS2 driver
> ras: mem: Add memory ACPI RAS2 driver
>
> Documentation/edac/scrub.rst | 73 ++++++
> drivers/acpi/Kconfig | 11 +
> drivers/acpi/Makefile | 1 +
> drivers/acpi/ras2.c | 417 +++++++++++++++++++++++++++++++++++
> drivers/ras/Kconfig | 11 +
> drivers/ras/Makefile | 1 +
> drivers/ras/acpi_ras2.c | 383 ++++++++++++++++++++++++++++++++
> include/acpi/ras2_acpi.h | 47 ++++
> 8 files changed, 944 insertions(+)
> create mode 100755 drivers/acpi/ras2.c
> create mode 100644 drivers/ras/acpi_ras2.c
> create mode 100644 include/acpi/ras2_acpi.h
>
next prev parent reply other threads:[~2025-03-03 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 12:27 shiju.jose
2025-02-28 12:27 ` [PATCH linux-next 1/2] ACPI:RAS2: Add ACPI RAS2 driver shiju.jose
2025-03-03 21:06 ` Yazen Ghannam
2025-03-04 16:59 ` Shiju Jose
2025-02-28 12:27 ` [PATCH linux-next 2/2] ras: mem: Add memory " shiju.jose
2025-03-03 9:35 ` Jonathan Cameron [this message]
2025-03-03 10:21 ` [PATCH linux-next 0/2] ACPI: Add support for ACPI RAS2 feature table Shiju Jose
2025-03-03 10:35 ` Borislav Petkov
2025-03-04 18:19 ` Shiju Jose
2025-03-04 20:30 ` Borislav Petkov
2025-03-04 20:46 ` Luck, Tony
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=20250303173538.000007cd@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Jon.Grimm@amd.com \
--cc=Vilas.Sridharan@amd.com \
--cc=Yazen.Ghannam@amd.com \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=dferguson@amperecomputing.com \
--cc=duenwen@google.com \
--cc=erdemaktas@google.com \
--cc=gthelen@google.com \
--cc=ira.weiny@intel.com \
--cc=j.williams@intel.com \
--cc=james.morse@arm.com \
--cc=jiaqiyan@google.com \
--cc=jthoughton@google.com \
--cc=kangkang.shen@futurewei.com \
--cc=lenb@kernel.org \
--cc=leo.duran@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=mchehab@kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=nifan.cxl@gmail.com \
--cc=pgonda@google.com \
--cc=prime.zeng@hisilicon.com \
--cc=rafael@kernel.org \
--cc=rientjes@google.com \
--cc=roberto.sassu@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=somasundaram.a@hpe.com \
--cc=tanxiaofei@huawei.com \
--cc=tony.luck@intel.com \
--cc=vishal.l.verma@intel.com \
--cc=wanghuiqiang@huawei.com \
--cc=wbs@os.amperecomputing.com \
--cc=wschwartz@amperecomputing.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