Linux-EDAC Archive mirror
 help / color / mirror / Atom feed
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>
Subject: RE: [PATCH 0/5] EDAC/igen6: Add EDAC support for several Intel SoCs with IBECC
Date: Tue, 5 Dec 2023 23:25:52 +0000	[thread overview]
Message-ID: <SJ1PR11MB60835628D38AD099BE401C47FC85A@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231113085318.26783-1-qiuxu.zhuo@intel.com>

> As these SoCs share similar IBECC registers, most of them are having
> compute die IDs added for EDAC support. There are some minor differences
> among them regarding IBECC presence detection, the number of memory
> controllers, and the most significant bit of the error address.

Applied series.  Thanks.

-Tony

      parent reply	other threads:[~2023-12-05 23:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13  8:53 [PATCH 0/5] EDAC/igen6: Add EDAC support for several Intel SoCs with IBECC Qiuxu Zhuo
2023-11-13  8:53 ` [PATCH 1/5] EDAC/igen6: Make get_mchbar() helper function Qiuxu Zhuo
2023-11-13  8:53 ` [PATCH 2/5] EDAC/igen6: Add Intel Alder Lake-N SoCs support Qiuxu Zhuo
2023-11-13  8:53 ` [PATCH 3/5] EDAC/igen6: Add Intel Raptor Lake-P " Qiuxu Zhuo
2023-11-13  8:53 ` [PATCH 4/5] EDAC/igen6: Add Intel Meteor Lake-PS " Qiuxu Zhuo
2023-11-13  8:53 ` [PATCH 5/5] EDAC/igen6: Add Intel Meteor Lake-P " Qiuxu Zhuo
2023-12-05 23:25 ` 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=SJ1PR11MB60835628D38AD099BE401C47FC85A@SJ1PR11MB6083.namprd11.prod.outlook.com \
    --to=tony.luck@intel.com \
    --cc=aris@redhat.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=qiuxu.zhuo@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 read-only IMAP folder(s) and NNTP newsgroup(s).