From: Borislav Petkov <bp@suse.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 5.1
Date: Tue, 5 Mar 2019 11:21:56 +0100 [thread overview]
Message-ID: <20190305102156.GD9073@zn.tnic> (raw)
Hi Linus,
please pull the following EDAC collection of patches for 5.1.
Thx.
The following changes since commit e6d429313ea5c776d2e76b4494df69102e6b7115:
x86/resctrl: Avoid confusion over the new X86_RESCTRL config (2019-02-02 10:34:52 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/edac_for_5.1
for you to fetch changes up to 580b5cf50ca8f4781961382d54959683341b3126:
EDAC/altera: Add separate SDRAM EDAC config (2019-02-26 16:18:57 +0100)
----------------------------------------------------------------
* A new EDAC AST 2500 SoC driver (Stefan M Schaeckeler)
* New i10nm EDAC driver for Intel 10nm CPUs (Qiuxu Zhuo and Tony Luck)
* Altera SDRAM functionality carveout for separate enablement of RAS and
SDRAM capabilities on some Altera chips. (Thor Thayer)
* The usual round of cleanups and fixes
Last but not least:
* Recruit James Morse as a reviewer for the ARM side
----------------------------------------------------------------
Borislav Petkov (2):
EDAC: Add James Morse as a reviewer
Merge remote-tracking branch 'tip/x86/urgent' into edac-for-5.1
Greg Kroah-Hartman (1):
EDAC: Do not check return value of debugfs_create() functions
Huang Zijiang (1):
EDAC, altera: Add missing of_node_put()
Qiuxu Zhuo (3):
EDAC, skx_common: Separate common code out from skx_edac
EDAC, skx_edac: Delete duplicated code
EDAC, i10nm: Add a driver for Intel 10nm server processors
Stefan M Schaeckeler (2):
EDAC, aspeed: Add an Aspeed AST2500 EDAC driver
dt-bindings, EDAC: Add Aspeed AST2500
Thor Thayer (1):
EDAC/altera: Add separate SDRAM EDAC config
Tony Luck (2):
EDAC, i10nm: Fix randconfig builds
EDAC, skx_common: Add code to recognise new compound error code
.../devicetree/bindings/edac/aspeed-sdram-edac.txt | 25 +
MAINTAINERS | 7 +
arch/arm/boot/dts/aspeed-g5.dtsi | 7 +
drivers/edac/Kconfig | 35 +-
drivers/edac/Makefile | 8 +-
drivers/edac/altera_edac.c | 72 +-
drivers/edac/aspeed_edac.c | 421 ++++++
drivers/edac/debugfs.c | 48 +-
drivers/edac/edac_module.h | 8 +-
drivers/edac/i10nm_base.c | 275 ++++
drivers/edac/skx_base.c | 650 ++++++++++
drivers/edac/skx_common.c | 691 ++++++++++
drivers/edac/skx_common.h | 152 +++
drivers/edac/skx_edac.c | 1358 --------------------
14 files changed, 2323 insertions(+), 1434 deletions(-)
create mode 100644 Documentation/devicetree/bindings/edac/aspeed-sdram-edac.txt
create mode 100644 drivers/edac/aspeed_edac.c
create mode 100644 drivers/edac/i10nm_base.c
create mode 100644 drivers/edac/skx_base.c
create mode 100644 drivers/edac/skx_common.c
create mode 100644 drivers/edac/skx_common.h
delete mode 100644 drivers/edac/skx_edac.c
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next reply other threads:[~2019-03-05 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 10:21 Borislav Petkov [this message]
2019-03-08 18:35 ` [GIT PULL] EDAC updates for 5.1 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=20190305102156.GD9073@zn.tnic \
--to=bp@suse.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