linux-kernel - Re: [GIT PULL] EFI changes for v3.11

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:	Mon, 08 Jul 2013 11:36:12 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Luck, Tony" <tony.luck@...el.com>
CC:	Matt Fleming <matt@...sole-pimps.org>,
	Ingo Molnar <mingo@...nel.org>,
	"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] EFI changes for v3.11

On 07/08/2013 10:29 AM, Luck, Tony wrote:
>>> ----------------------------------------------------------------
>>> Tony Luck (1):
>>>       [IA64] sim: Add casts to avoid assignment warnings
>>>
>>>  arch/ia64/hp/sim/boot/fw-emu.c | 20 ++++++++++----------
>>>  1 file changed, 10 insertions(+), 10 deletions(-)
>>
>> I don't see this commit in Linus' tree so presumably Tony is still
>> seeing these warnings.
> 
> Correct - I see 10 warning about "assignment makes pointer from integer"
> when building Linus' tree (HEAD = d2b4a646).
> 
> My patch doesn't appear to be in linux-next either (next-20130708).
> 
> I had hoped to have this patch follow in the same path that the
> one that changed the types and introduced the warnings took ...
> but since that didn't work perhaps I should just ask Linus to pull
> it from my ia64 tree.
> 

I can push it, although it seems a bit odd to me to push an ia64-only
patch through the x86 tree.

Let me know what you prefer.

	-hpa


--
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/