From: Tony Luck <tony.luck@intel.com>
To: linux-kernel@vger.kernel.org
Cc: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Borislav Petkov <bp@suse.de>,
Chen Gong <gong.chen@linux.intel.com>
Subject: [PATCH 0/2] machine check decode fixes
Date: Wed, 24 Jul 2013 13:58:12 -0700 [thread overview]
Message-ID: <cover.1374699492.git.tony.luck@intel.com> (raw)
V2 of this:
* Broken into two patches - by suggestion of Chen Gong
* Just change MCACOD #define value - by suggestion of Naveen
Tony Luck (2):
x86/mce: Fix mce regression from recent cleanup
x86/mce: Pay no attention to 'F' bit in MCACOD when parsing 'UC'
errors
arch/x86/include/asm/mce.h | 13 +++++++++++--
arch/x86/kernel/cpu/mcheck/mce-severity.c | 4 ++--
2 files changed, 13 insertions(+), 4 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-07-24 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 20:58 Tony Luck [this message]
2013-07-24 17:09 ` [PATCH 1/2] x86/mce: Fix mce regression from recent cleanup Tony Luck
2013-07-24 20:54 ` [PATCH 2/2] x86/mce: Pay no attention to 'F' bit in MCACOD when parsing 'UC' errors Tony Luck
2013-07-25 10:40 ` [PATCH 0/2] machine check decode fixes Naveen N. Rao
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=cover.1374699492.git.tony.luck@intel.com \
--to=tony.luck@intel.com \
--cc=bp@suse.de \
--cc=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
/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.