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 6.3
Date: Sat, 18 Feb 2023 15:59:49 +0100 [thread overview]
Message-ID: <Y/Dn5bXwGxiDh8RI@zn.tnic> (raw)
Hi Linus,
please pull the pile of EDAC updates for 6.3. I'm sending a bit early
but I know you prefer that.
Thx.
---
The following changes since commit b7bfaa761d760e72a969d116517eaa12e404c262:
Linux 6.2-rc3 (2023-01-08 11:49:43 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git tags/edac_updates_for_v6.3
for you to fetch changes up to 28980db94742f9f2fb0f68ea35f2171b38007bae:
EDAC/amd64: Shut up an -Werror,-Wsometimes-uninitialized clang false positive (2023-02-14 17:56:14 +0100)
----------------------------------------------------------------
- Add a driver for the RAS functionality on Xilinx's on chip memory
controller
- Add support for decoding errors from the first and second level memory
on SKL-based hardware
- Add support for the memory controllers in Intel Granite Rapids and
Emerald Rapids machines
- First round of amd64_edac driver simplification and removal of
unneeded functionality
- The usual cleanups and fixes
----------------------------------------------------------------
Manivannan Sadhasivam (1):
EDAC/qcom: Add platform_device_id table for module autoloading
Qiuxu Zhuo (5):
EDAC/skx_common: Enable EDAC support for the "near" memory
EDAC/skx_common: Delete duplicated and unreachable code
EDAC/i10nm: Add Intel Emerald Rapids server support
EDAC/i10nm: Make more configurations CPU model specific
EDAC/i10nm: Add Intel Granite Rapids server support
Sai Krishna Potthuri (1):
EDAC/zynqmp: Add EDAC support for Xilinx ZynqMP OCM
Shubhrajyoti Datta (1):
dt-bindings: edac: Add bindings for Xilinx ZynqMP OCM
Yazen Ghannam (6):
EDAC/amd64: Don't set up EDAC PCI control on Family 17h+
EDAC/amd64: Remove scrub rate control for Family 17h and later
EDAC/amd64: Remove PCI Function 6
EDAC/amd64: Remove PCI Function 0
EDAC/amd64: Remove early_channel_count()
EDAC/amd64: Shut up an -Werror,-Wsometimes-uninitialized clang false positive
Youquan Song (1):
EDAC/i10nm: Add driver decoder for Sapphire Rapids server
.../memory-controllers/xlnx,zynqmp-ocmc-1.0.yaml | 45 ++
MAINTAINERS | 7 +
drivers/edac/Kconfig | 8 +
drivers/edac/Makefile | 1 +
drivers/edac/amd64_edac.c | 217 +---------
drivers/edac/amd64_edac.h | 24 +-
drivers/edac/i10nm_base.c | 459 ++++++++++++++++----
drivers/edac/qcom_edac.c | 7 +
drivers/edac/skx_common.c | 76 ++--
drivers/edac/skx_common.h | 61 ++-
drivers/edac/zynqmp_edac.c | 467 +++++++++++++++++++++
11 files changed, 1013 insertions(+), 359 deletions(-)
create mode 100644 Documentation/devicetree/bindings/memory-controllers/xlnx,zynqmp-ocmc-1.0.yaml
create mode 100644 drivers/edac/zynqmp_edac.c
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2023-02-18 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 14:59 Borislav Petkov [this message]
2023-02-21 17:24 ` [GIT PULL] EDAC updates for 6.3 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=Y/Dn5bXwGxiDh8RI@zn.tnic \
--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;
as well as URLs for NNTP newsgroup(s).