From: "Jan Beulich" <JBeulich@suse.com>
To: stefano.stabellini@eu.citrix.com
Cc: david.vrabel@citrix.com, ian.campbell@citrix.com,
jeremy@goop.org, fenghua.yu@intel.com, matt.fleming@intel.com,
tony.luck@intel.com, x86@kernel.org, tglx@linutronix.de,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
Daniel Kiper <daniel.kiper@oracle.com>,
konrad.wilk@oracle.com, Tang Liang <liang.tang@oracle.com>,
eshelton@pobox.com, mingo@redhat.com, linux-efi@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
hpa@zytor.com
Subject: Re: [PATCH v3 4/5] xen: Define EFI related stuff
Date: Wed, 26 Mar 2014 15:25:16 +0000 [thread overview]
Message-ID: <5332FF6C02000078000027A5@nat28.tlf.novell.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1403261452160.2747@kaball.uk.xensource.com>
>>> On 26.03.14 at 15:58, <stefano.stabellini@eu.citrix.com> wrote:
>> +struct xenpf_efi_runtime_call {
>> + uint32_t function;
>> + /*
>> + * This field is generally used for per sub-function flags (defined
>> + * below), except for the XEN_EFI_get_next_high_monotonic_count case,
>> + * where it holds the single returned value.
>> + */
>> + uint32_t misc;
>> + unsigned long status;
>
> I realize that this is just the same as xen/include/public/platform.h,
> but this field should be xen_ulong_t.
Care to supply a patch to the canonical header?
Jan
next prev parent reply other threads:[~2014-03-26 15:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 20:57 [PATCH v3 0/5] xen: Add EFI support Daniel Kiper
2014-03-25 20:57 ` [PATCH v3 1/5] efi: Add efi_init_ops variable Daniel Kiper
2014-03-26 12:56 ` Matt Fleming
2014-03-26 14:02 ` Daniel Kiper
2014-03-26 14:29 ` Matt Fleming
2014-03-25 20:57 ` [PATCH v3 2/5] efi: Export arch_tables variable Daniel Kiper
2014-03-26 13:21 ` Jan Beulich
2014-03-26 14:08 ` Daniel Kiper
2014-03-26 14:17 ` Jan Beulich
2014-03-26 14:18 ` Matt Fleming
2014-03-25 20:57 ` [PATCH v3 3/5] x86: Call efi_memblock_x86_reserve_range() on native EFI platform only Daniel Kiper
2014-03-26 13:00 ` Matt Fleming
2014-03-26 13:22 ` Jan Beulich
2014-03-26 13:31 ` Matt Fleming
2014-03-26 13:39 ` Jan Beulich
2014-03-26 13:48 ` Daniel Kiper
2014-03-26 13:57 ` Matt Fleming
2014-03-26 22:01 ` Daniel Kiper
2014-03-26 22:35 ` [Xen-devel] [PATCH v3 3/5] x86: Call efi_memblock_x86_reserve_range() on native EFI platform onl Andrew Cooper
2014-03-25 20:57 ` [PATCH v3 4/5] xen: Define EFI related stuff Daniel Kiper
2014-03-26 13:25 ` Jan Beulich
2014-03-26 14:58 ` Stefano Stabellini
2014-03-26 15:25 ` Jan Beulich [this message]
2014-03-26 15:34 ` Stefano Stabellini
2014-03-25 20:57 ` [PATCH v3 5/5] xen: Put EFI machinery in place Daniel Kiper
2014-03-26 13:12 ` Matt Fleming
2014-03-26 13:31 ` Jan Beulich
2014-03-26 13:46 ` Matt Fleming
2014-03-26 13:53 ` Matt Fleming
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=5332FF6C02000078000027A5@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=daniel.kiper@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=eshelton@pobox.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=liang.tang@oracle.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@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