From: "Jan Beulich" <JBeulich@suse.com>
To: <david.vrabel@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, <boris.ostrovsky@oracle.com>,
"Juergen Gross" <JGross@suse.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen/mcelog: also build for x86-32
Date: Thu, 07 Jul 2016 03:46:24 -0600 [thread overview]
Message-ID: <577E411002000078000FC0EE@prv-mh.provo.novell.com> (raw)
In-Reply-To: <577E2383.60908@citrix.com>
>>> On 07.07.16 at 11:40, <david.vrabel@citrix.com> wrote:
> 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?
Well, its original version in the 2.6.18 tree did get enabled for 32-bit
use in the course of forward porting those patches, and things work
there. I don't have a 32-bit pv-ops Dom0 setup anywhere. So feel
free to ignore this patch.
Jan
prev parent reply other threads:[~2016-07-07 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 7:35 Jan Beulich
2016-07-07 9:40 ` [Xen-devel] " David Vrabel
2016-07-07 9:46 ` Jan Beulich [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=577E411002000078000FC0EE@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=JGross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.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
all inboxes | Powered by JetHome®