mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kyle Manna" <kyle@kylemanna.com>
To: "Tony Luck" <tony.luck@intel.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Jason Baron" <jbaron@akamai.com>,
	"Qiuxu Zhuo" <qiuxu.zhuo@intel.com>
Cc: "James Jernigan" <jameswestonjernigan@gmail.com>,
	"James Morse" <james.morse@arm.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Robert Richter" <rric@kernel.org>, "Yi1 Lai" <yi1.lai@intel.com>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] EDAC/ie31200: Add two more Intel Alder Lake-S SoCs for EDAC support
Date: Mon, 11 Aug 2025 08:50:14 -0700	[thread overview]
Message-ID: <c2f98618-4197-41c3-9a2b-2c59841dd543@app.fastmail.com> (raw)
In-Reply-To: <20250802060112.363506-1-kyle@kylemanna.com>

On Fri, Aug 1, 2025, at 23:01, Kyle Manna wrote:
> Host Device IDs (DID0) correspond to:
> * Intel Core i7-12700K
> * Intel Core i5-12600K
>
> See documentation:
> * 12th Generation Intel® Core™ Processors Datasheet
>     * Volume 1 of 2, Doc. No.: 655258, Rev.: 011
>     * https://edc.intel.com/output/DownloadPdfDocument?id=8297 (PDF)
>
> Signed-off-by: Kyle Manna <kyle@kylemanna.com>
> Reviewed-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
> ---
> Changes in v2:
> - Rebased on top of a6923c06a3b2e2c534ae28c53a7531e76cc95cfa
> - Added comments to Device ID definitions as requested
> - Added Reviewed-by tag from Qiuxu Zhuo
>
>  drivers/edac/ie31200_edac.c | 4 ++++
>  1 file changed, 4 insertions(+)

Hi Tony, Jason,

Gentle ping on this small EDAC/ie31200 change that adds two more Alder Lake-S device IDs for ECC-capable part.

Reviewed-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>

Could you please pick this up for the EDAC tree (ras edac-for-next)?

Thanks,
- Kyle

  reply	other threads:[~2025-08-11 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-02  6:01 Kyle Manna
2025-08-11 15:50 ` Kyle Manna [this message]
2025-08-11 16:33   ` howtobserve1

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=c2f98618-4197-41c3-9a2b-2c59841dd543@app.fastmail.com \
    --to=kyle@kylemanna.com \
    --cc=bp@alien8.de \
    --cc=james.morse@arm.com \
    --cc=jameswestonjernigan@gmail.com \
    --cc=jbaron@akamai.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=tony.luck@intel.com \
    --cc=yi1.lai@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

all inboxes | Powered by JetHome®