From: Chen Gong <gong.chen@linux.intel.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
"bp@alien8.de" <bp@alien8.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/MCE: Update MCE severity condition check
Date: Wed, 26 Jun 2013 05:18:08 -0400 [thread overview]
Message-ID: <20130626091808.GA18468@gchen.bj.intel.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31C53805@ORSMSX106.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On Tue, Jun 25, 2013 at 04:31:23PM +0000, Luck, Tony wrote:
> Date: Tue, 25 Jun 2013 16:31:23 +0000
> From: "Luck, Tony" <tony.luck@intel.com>
> To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>, Chen Gong
> <gong.chen@linux.intel.com>
> CC: "bp@alien8.de" <bp@alien8.de>, "linux-kernel@vger.kernel.org"
> <linux-kernel@vger.kernel.org>
> Subject: RE: [PATCH] x86/MCE: Update MCE severity condition check
>
> > The SDM talks about "non-affected" logical processors, but perhaps we
> > can call this an "unaffected" thread?
>
> "unaffected" sounds a bit more natural (but close enough to the wording in
> the SDM that people should see the connection).
>
> -Tony
If this patch is OK, would you please help to update it when merging
it? Thanks very much.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-26 9:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 9:16 [PATCH] x86/MCE: Update MCE severity condition check Chen Gong
2013-06-20 9:41 ` Borislav Petkov
2013-06-21 12:38 ` Chen Gong
2013-06-25 6:32 ` Naveen N. Rao
2013-06-25 16:31 ` Luck, Tony
2013-06-25 20:08 ` Naveen N. Rao
2013-06-26 9:18 ` Chen Gong [this message]
[not found] ` <0134840@agluck-desk.sc.intel.com>
2013-06-26 19:08 ` [PATCH] x86/mce: " Borislav Petkov
2013-06-26 20:23 ` Luck, Tony
2013-06-26 20:36 ` Borislav Petkov
2013-06-26 21:00 ` Luck, Tony
2013-06-26 21:10 ` Borislav Petkov
2013-06-27 6:42 ` Chen Gong
2013-06-27 8:55 ` 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=20130626091808.GA18468@gchen.bj.intel.com \
--to=gong.chen@linux.intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=tony.luck@intel.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.