mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-edac <linux-edac@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] EDAC updates for v6.16
Date: Sun, 25 May 2025 23:16:18 +0200	[thread overview]
Message-ID: <20250525211618.GAaDOIolEntC03ernr@fat_crate.local> (raw)

Hi Linus,

please pull the EDAC updates for v6.16.

Thx.

---

The following changes since commit 8ffd015db85fea3e15a77027fda6c02ced4d2444:

  Linux 6.15-rc2 (2025-04-13 11:54:49 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git tags/edac_updates_for_v6.16

for you to fetch changes up to ea3b0b7f541b9511abe2b89547c95458804f38e2:

  EDAC/bluefield: Don't use bluefield_edac_readl() result on error (2025-05-22 17:58:28 +0200)

----------------------------------------------------------------
- ie31200: Add support for Raptor Lake-S and Alder Lake-S compute dies

- Rework how RRL registers per channel tracking is done in order to
  support newer hardware with different RRL configurations and refactor
  that code. Add support for Granite Rapids server

- i10nm: explicitly set RRL modes to fix any wrong BIOS programming

- Properly save and restore Retry Read error Log channel configuration
  info on Intel drivers

- igen6: Handle correctly the case of fused off memory controllers on
  Arizona Beach and Amston Lake SoCs before adding support for them

- the usual set of fixes and cleanups

----------------------------------------------------------------
David Thompson (1):
      EDAC/bluefield: Don't use bluefield_edac_readl() result on error

Qiuxu Zhuo (12):
      EDAC/igen6: Skip absent memory controllers
      EDAC/igen6: Add Intel Arizona Beach SoCs support
      EDAC/igen6: Add Intel Amston Lake SoCs support
      EDAC/skx_common: Fix general protection fault
      EDAC/{skx_common,i10nm}: Fix the loss of saved RRL for HBM pseudo channel 0
      EDAC/i10nm: Explicitly set the modes of the RRL register sets
      EDAC/{skx_common,i10nm}: Structure the per-channel RRL registers
      EDAC/{skx_common,i10nm}: Refactor enable_retry_rd_err_log()
      EDAC/{skx_common,i10nm}: Refactor show_retry_rd_err_log()
      EDAC/{skx_common,i10nm}: Add RRL support for Intel Granite Rapids server
      EDAC/ie31200: Add two Intel SoCs for EDAC support
      EDAC/i10nm: Fix the bitwise operation between variables of different sizes

 drivers/edac/bluefield_edac.c |  20 +-
 drivers/edac/i10nm_base.c     | 479 ++++++++++++++++++++++++------------------
 drivers/edac/ie31200_edac.c   |   6 +
 drivers/edac/igen6_edac.c     |  86 ++++++--
 drivers/edac/skx_common.c     |   1 +
 drivers/edac/skx_common.h     |  61 +++++-
 6 files changed, 422 insertions(+), 231 deletions(-)


-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

             reply	other threads:[~2025-05-25 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25 21:16 Borislav Petkov [this message]
2025-05-27 17:26 ` pr-tracker-bot

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=20250525211618.GAaDOIolEntC03ernr@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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®