From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] RAS changes for v4.17
Date: Mon, 2 Apr 2018 10:26:54 +0200 [thread overview]
Message-ID: <20180402082654.nyyzqno5pzrccrtk@gmail.com> (raw)
Linus,
Please pull the latest ras-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-core-for-linus
# HEAD: e2efacb6a54ab54626da3507be1008d0040492cc Revert "x86/mce/AMD: Collect error info even if valid bits are not set"
The main changes in this cycle were:
- AMD MCE support/decoding improvements (Yazen Ghannam)
- general MCE header cleanups and reorganization (Borislav Petkov)
Thanks,
Ingo
------------------>
Borislav Petkov (5):
x86/mce: Put private structures and definitions into the internal header
x86/mce: Convert 'struct mca_config' bools to a bitfield
x86/mce: Issue the 'mcelog --ascii' message only on !AMD
x86/mce/AMD: Collect error info even if valid bits are not set
x86/MCE: Cleanup and complete struct mce fields definitions
Yazen Ghannam (5):
x86/mce/AMD: Pass the bank number to smca_get_bank_type()
x86/mce/AMD, EDAC/mce_amd: Enumerate Reserved SMCA bank type
x86/mce/AMD: Get address from already initialized block
x86/mce/AMD: Carve out SMCA get_block_address() code
Revert "x86/mce/AMD: Collect error info even if valid bits are not set"
arch/x86/include/asm/mce.h | 53 +--------------------
arch/x86/include/uapi/asm/mce.h | 52 +++++++++++----------
arch/x86/kernel/cpu/mcheck/mce-internal.h | 59 ++++++++++++++++++++++-
arch/x86/kernel/cpu/mcheck/mce.c | 20 ++++----
arch/x86/kernel/cpu/mcheck/mce_amd.c | 78 ++++++++++++++++++++-----------
drivers/edac/mce_amd.c | 11 +++--
6 files changed, 156 insertions(+), 117 deletions(-)
reply other threads:[~2018-04-02 8:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180402082654.nyyzqno5pzrccrtk@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.