From: "Luck, Tony" <tony.luck@intel.com>
To: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
Aristeu Rozanski <aris@redhat.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Li, Lili" <lili.li@intel.com>,
"ricardo.neri-calderon@linux.intel.com"
<ricardo.neri-calderon@linux.intel.com>
Subject: RE: [PATCH 0/2] EDAC/{igen6,i10nm}: Add EDAC support for two Intel CPUs
Date: Thu, 1 Feb 2024 20:47:02 +0000 [thread overview]
Message-ID: <SJ1PR11MB6083A37E3A43C7055B5B4203FC432@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240129062040.60809-1-qiuxu.zhuo@intel.com>
> Both patches solely add CPU IDs for EDAC support.
>
> - Part1: Add a new Alder Lake-N SoC compute die ID for EDAC support.
> - Part2: Add the Grand Ridge (micro-server) CPU model ID for EDAC support.
>
> Lili Li (1):
> EDAC/igen6: Add one more Intel Alder Lake-N SoC support
>
> Qiuxu Zhuo (1):
> EDAC/i10nm: Add Intel Grand Ridge micro-server support
Applied both patches.
Thanks
-Tony
prev parent reply other threads:[~2024-02-01 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 6:20 [PATCH 0/2] EDAC/{igen6,i10nm}: Add EDAC support for two Intel CPUs Qiuxu Zhuo
2024-01-29 6:20 ` [PATCH 1/2] EDAC/igen6: Add one more Intel Alder Lake-N SoC support Qiuxu Zhuo
2024-01-29 6:20 ` [PATCH 2/2] EDAC/i10nm: Add Intel Grand Ridge micro-server support Qiuxu Zhuo
2024-01-30 2:45 ` [PATCH 0/2] EDAC/{igen6,i10nm}: Add EDAC support for two Intel CPUs Ricardo Neri
2024-02-01 20:47 ` Luck, Tony [this message]
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=SJ1PR11MB6083A37E3A43C7055B5B4203FC432@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.com \
--cc=aris@redhat.com \
--cc=bp@alien8.de \
--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=ricardo.neri-calderon@linux.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;
as well as URLs for NNTP newsgroup(s).