linux-kernel - Re: [PATCH v3 4/5] xen: Define EFI related stuff

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 26 Mar 2014 15:25:16 +0000
From:	"Jan Beulich" <JBeulich@...e.com>
To:	<stefano.stabellini@...citrix.com>
Cc:	<david.vrabel@...rix.com>, <ian.campbell@...rix.com>,
	<jeremy@...p.org>, <fenghua.yu@...el.com>,
	<matt.fleming@...el.com>, <tony.luck@...el.com>, <x86@...nel.org>,
	<tglx@...utronix.de>, <xen-devel@...ts.xenproject.org>,
	<boris.ostrovsky@...cle.com>,
	"Daniel Kiper" <daniel.kiper@...cle.com>, <konrad.wilk@...cle.com>,
	"Tang Liang" <liang.tang@...cle.com>, <eshelton@...ox.com>,
	<mingo@...hat.com>, <linux-efi@...r.kernel.org>,
	<linux-ia64@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<hpa@...or.com>
Subject: Re: [PATCH v3 4/5] xen: Define EFI related stuff

>>> On 26.03.14 at 15:58, <stefano.stabellini@...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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/