From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tony Luck <tony.luck@intel.com>, x86-ml <x86@kernel.org>,
linux-edac <linux-edac@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] RAS updates for 5.4
Date: Fri, 13 Sep 2019 10:10:39 +0200 [thread overview]
Message-ID: <20190913080937.GB20745@zn.tnic> (raw)
Hi Linus,
please pull this branch
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-core-for-linus
to receive the latest meager RAS updates for 5.4:
- Enable processing of action-optional MCEs which have the Overflow bit set
(Tony Luck)
- -Wmissing-prototypes warning fix and a build fix (Valdis Klētnieks)
Thx.
---
The following changes since commit e21a712a9685488f5ce80495b37b9fdbe96c230d:
Linux 5.3-rc3 (2019-08-04 18:40:12 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-core-for-linus
for you to fetch changes up to b6ff24f7b5101101ff897dfdde3f37924e676bc2:
RAS: Build debugfs.o only when enabled in Kconfig (2019-08-08 17:44:02 +0200)
----------------------------------------------------------------
Tony Luck (1):
x86/mce: Don't check for the overflow bit on action optional machine checks
Valdis Kletnieks (2):
RAS: Fix prototype warnings
RAS: Build debugfs.o only when enabled in Kconfig
arch/x86/kernel/cpu/mce/severity.c | 4 ++--
drivers/ras/Makefile | 3 ++-
drivers/ras/cec.c | 1 +
drivers/ras/debugfs.c | 2 ++
4 files changed, 7 insertions(+), 3 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 247165, AG München
next reply other threads:[~2019-09-13 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 8:10 Borislav Petkov [this message]
2019-09-16 21:35 ` [GIT PULL] RAS updates for 5.4 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=20190913080937.GB20745@zn.tnic \
--to=bp@suse.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).