From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ras/core for 5.19
Date: Mon, 23 May 2022 13:16:20 +0200 [thread overview]
Message-ID: <YottBBImBRUl5LQS@zn.tnic> (raw)
Hi Linus,
please pull a couple of RAS updates for 5.19.
Thx.
---
The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/ras_core_for_v5.19_rc1
for you to fetch changes up to fa619f5156cf1ee3773edc6d756be262c9ef35de:
x86/mce: Add messages for panic errors in AMD's MCE grading (2022-04-25 12:40:48 +0200)
----------------------------------------------------------------
- Simplification of the AMD MCE error severity grading logic along with
supplying critical panic MCEs with accompanying error messages for more
human-friendly diagnostics.
- Misc fixes
----------------------------------------------------------------
Ammar Faizi (1):
x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails
Carlos Bilbao (2):
x86/mce: Simplify AMD severity grading logic
x86/mce: Add messages for panic errors in AMD's MCE grading
Smita Koralahalli (1):
x86/mce: Avoid unnecessary padding in struct mce_bank
arch/x86/kernel/cpu/mce/amd.c | 32 ++++++-----
arch/x86/kernel/cpu/mce/core.c | 4 +-
arch/x86/kernel/cpu/mce/severity.c | 110 +++++++++++++++----------------------
3 files changed, 67 insertions(+), 79 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
next reply other threads:[~2022-05-23 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 11:16 Borislav Petkov [this message]
2022-05-24 2:51 ` [GIT PULL] ras/core for 5.19 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=YottBBImBRUl5LQS@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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