From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
david.vrabel@citrix.com, boris.ostrovsky@oracle.com,
Juergen Gross <JGross@suse.com>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/mcelog: also build for x86-32
Date: Thu, 7 Jul 2016 10:40:19 +0100 [thread overview]
Message-ID: <577E2383.60908__9727.38532950661$1467884494$gmane$org@citrix.com> (raw)
In-Reply-To: <577E226702000078000FBDC5@prv-mh.provo.novell.com>
On 07/07/16 08:35, Jan Beulich wrote:
> There's no reason why this would need to be limited to x86-64.
Did you test it?
David
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-07 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 7:35 [PATCH] xen/mcelog: also build for x86-32 Jan Beulich
2016-07-07 9:40 ` David Vrabel [this message]
[not found] ` <577E2383.60908@citrix.com>
2016-07-07 9:46 ` Jan Beulich
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='577E2383.60908__9727.38532950661$1467884494$gmane$org@citrix.com' \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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).