From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Konrad Rzeszutek Wilk <konrad@darnok.org>
Cc: "Liu, Jinsong" <jinsong.liu@intel.com>,
"Brown, Len" <len.brown@intel.com>,
"jeremy.fitzhardinge@citrix.com" <jeremy.fitzhardinge@citrix.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>,
"Shan, Haitao" <haitao.shan@intel.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
"Zhao, Yakui" <yakui.zhao@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
"Kleen, Andi" <andi.kleen@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Xen-devel] [PATCH 01/10] Add mcelog support from xen platform
Date: Tue, 3 Jan 2012 15:39:12 -0500 [thread overview]
Message-ID: <20120103203912.GG17472@phenom.dumpdata.com> (raw)
In-Reply-To: <20111223124208.GA25286@andromeda.dapyr.net>
On Fri, Dec 23, 2011 at 08:42:08AM -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, Dec 23, 2011 at 10:23:03AM +0000, Liu, Jinsong wrote:
> > >From 0e8de1ce0f13aa34aa6013e6a387ae5be78031ca Mon Sep 17 00:00:00 2001
> > From: Liu Jinsong <jinsong.liu@intel.com>
> > Date: Tue, 6 Dec 2011 18:08:12 +0800
> > Subject: [PATCH 01/10] Add mcelog support from xen platform
>
> .. for xen platform.
> >
> > This patch backport from Jeremy's pvops commit a5ed1f3dae179158e385e9371462dd65d5e125c5,
> > which in turn backport from previous xen DOM0(2.6.18) cs: 75e5bfa7fbdc
>
> Ok. You should also include a link to the tree.
Actually on a second thought we don't need it. This patch (and all the others)
have never been posted upstream. So the back-history is not really that interesting
unless there has been a lot of churn (say the authorship changed or you had to
redo some serious surgery on it).
prev parent reply other threads:[~2012-01-03 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 10:23 [PATCH 01/10] Add mcelog support from xen platform Liu, Jinsong
2011-12-23 12:42 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-01-03 20:39 ` Konrad Rzeszutek Wilk [this message]
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=20120103203912.GG17472@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=andi.kleen@intel.com \
--cc=haitao.shan@intel.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=jinsong.liu@intel.com \
--cc=konrad@darnok.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yakui.zhao@intel.com \
--cc=yunhong.jiang@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 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).