From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: Borislav Petkov <bp@amd64.org>,
"Luck, Tony" <tony.luck@intel.com>,
"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] xen/mce: Add mcelog support for Xen platform
Date: Thu, 31 May 2012 12:11:39 -0400 [thread overview]
Message-ID: <20120531161139.GA13939@phenom.dumpdata.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC82923351FEE7C@SHSMSX101.ccr.corp.intel.com>
On Thu, May 31, 2012 at 12:57:44PM +0000, Liu, Jinsong wrote:
> >From 1a7951d6ca01d7f2c9dd2bdb6de5f8e7fdcb8bbd Mon Sep 17 00:00:00 2001
> From: root <root@ljsromley.bj.intel.com>
Also your git author is busted. I fixed it up for you but
you might want to run 'git config --user.name' and such
> Date: Fri, 1 Jun 2012 03:12:51 +0800
> Subject: [PATCH 1/2] xen/mce: Add mcelog support for Xen platform
What about the cvt_gate_to_trap? Does that need something similar
to "xen/mce: Register native mce handler as vMCE bounce back point"
?
I stuck all these patches on devel/mce.v2 on
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
next prev parent reply other threads:[~2012-05-31 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 12:57 [PATCH 1/2] xen/mce: Add mcelog support for Xen platform Liu, Jinsong
2012-05-31 13:50 ` Borislav Petkov
2012-05-31 15:30 ` Konrad Rzeszutek Wilk
2012-05-31 16:11 ` Konrad Rzeszutek Wilk [this message]
2012-05-31 17:27 ` Liu, Jinsong
2012-05-31 17:31 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-05-31 18:08 ` Liu, Jinsong
2012-05-31 18:54 ` Konrad Rzeszutek Wilk
2012-06-01 7:57 ` Liu, Jinsong
2012-06-06 20:55 ` Konrad Rzeszutek Wilk
2012-06-07 6:45 ` Liu, Jinsong
2012-06-07 17:20 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-06-08 9:27 ` Liu, Jinsong
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=20120531161139.GA13939@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bp@amd64.org \
--cc=jinsong.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=xen-devel@lists.xensource.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 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).