From: "Luck, Tony" <tony.luck@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] x86/mce recovery cleanup patch
Date: Thu, 23 Feb 2012 11:45:40 -0800 [thread overview]
Message-ID: <4f46976434651797d@agluck-desktop.sc.intel.com> (raw)
Ingo,
This is the patch to replace some hard coded constants that we discussed
here: https://lkml.org/lkml/2012/1/27/127
I'd coded it up four weeks ago, but forgot to send you a pull. This
goes on top of the previous patchset for mce recovery that is sitting
in your x86/mce branch of the tip tree waiting for the 3.4 merge window.
-Tony
The following changes since commit 5f7b88d51e89771f64c15903b96b5933dd0bc6d8:
x86/mce: Recognise machine check bank signature for data path error (2012-01-03 12:07:07 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git mce-recovery-for-tip
for you to fetch changes up to 08dda402d60a721ac94e79efd7646b332be3e3b2:
x86/mce: Replace hard coded hex constants with symbolic defines (2012-01-26 16:02:22 -0800)
----------------------------------------------------------------
Symbolic defines for architectural MCACOD constants
----------------------------------------------------------------
Tony Luck (1):
x86/mce: Replace hard coded hex constants with symbolic defines
arch/x86/kernel/cpu/mcheck/mce-severity.c | 14 ++++++++++----
1 files changed, 10 insertions(+), 4 deletions(-)
next reply other threads:[~2012-02-23 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 19:45 Luck, Tony [this message]
2012-02-24 15:27 ` [GIT PULL] x86/mce recovery cleanup patch Ingo Molnar
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=4f46976434651797d@agluck-desktop.sc.intel.com \
--to=tony.luck@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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