From: "Luck, Tony" <tony.luck@intel.com>
To: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
Cc: Borislav Petkov <bp@alien8.de>, James Morse <james.morse@arm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Richter <rric@kernel.org>, Lili Li <lili.li@intel.com>,
Laurens SEGHERS <laurens@rale.com>,
VikasX Chougule <vikasx.chougule@intel.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] EDAC: Add three Intel CPUs for EDAC support
Date: Mon, 7 Jul 2025 11:03:47 -0700 [thread overview]
Message-ID: <aGwMA0jZWbQeBIuZ@agluck-desk3> (raw)
In-Reply-To: <20250704151609.7833-1-qiuxu.zhuo@intel.com>
On Fri, Jul 04, 2025 at 11:16:06PM +0800, Qiuxu Zhuo wrote:
> Add EDAC support for three Intel CPUs:
>
> - Patch 1: Wildcat Lake SoCs with In-Band ECC.
> - Patch 2: Granite Rapids-D for micro-server and edge computing applications.
> - Patch 3: Raptor Lake HX series SoCs with Out-of-Band ECC.
>
> This patch series is on top of RAS edac-drivers branch.
>
> Lili Li (1):
> EDAC/igen6: Add Intel Wildcat Lake SoCs support
>
> Qiuxu Zhuo (2):
> EDAC/i10nm: Add Intel Granite Rapids-D support
> EDAC/ie31200: Add Intel Raptor Lake-HX SoCs support
>
> drivers/edac/i10nm_base.c | 12 +++++++++++-
> drivers/edac/ie31200_edac.c | 4 ++++
> drivers/edac/igen6_edac.c | 15 +++++++++++++++
> 3 files changed, 30 insertions(+), 1 deletion(-)
Added all three to RAS tree, branch edac-drivers.
Thanks
-Tony
next prev parent reply other threads:[~2025-07-07 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 15:16 [PATCH 0/3] EDAC: Add three Intel CPUs for EDAC support Qiuxu Zhuo
2025-07-04 15:16 ` [PATCH 1/3] EDAC/i10nm: Add Intel Granite Rapids-D support Qiuxu Zhuo
2025-07-04 15:16 ` [PATCH 2/3] EDAC/igen6: Add Intel Wildcat Lake SoCs support Qiuxu Zhuo
2025-07-04 15:16 ` [PATCH 3/3] EDAC/ie31200: Add Intel Raptor Lake-HX " Qiuxu Zhuo
2025-07-07 18:03 ` Luck, Tony [this message]
2025-07-08 13:19 ` [PATCH 0/3] EDAC: Add three Intel CPUs for EDAC support Zhuo, Qiuxu
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=aGwMA0jZWbQeBIuZ@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=laurens@rale.com \
--cc=lili.li@intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rric@kernel.org \
--cc=vikasx.chougule@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox