On Mon, Apr 16, 2018 at 02:07:25PM +0200, Ard Biesheuvel wrote: > > On 16 Apr 2018, at 13:40, Daniel Kiper <[email protected]> wrote: > >> On Mon, Apr 16, 2018 at 07:02:15PM +0800, kbuild test robot wrote: > >> tree: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next > >> head: 2c603650ee23c4596f4852e43ae40e42a0c771e1 > >> commit: 2c603650ee23c4596f4852e43ae40e42a0c771e1 [1/1] x86/xen/efi: > >> Initialize UEFI secure boot state during dom0 boot > >> reproduce: > >> # apt-get install sparse > >> git checkout 2c603650ee23c4596f4852e43ae40e42a0c771e1 > >> make ARCH=x86_64 allmodconfig > >> make C=1 CF=-D__CHECK_ENDIAN__ > >> > >> > >> sparse warnings: (new ones prefixed by >>) > >> > >>>> arch/x86/xen/efi.c:133:35: sparse: incorrect type in argument 1 > >>>> (different type sizes) @@ expected unsigned short [usertype] *name @@ > >>>> got ype] *name @@ > >> arch/x86/xen/efi.c:133:35: expected unsigned short [usertype] *name > >> arch/x86/xen/efi.c:133:35: got char *<noident> > >> arch/x86/xen/efi.c:143:35: sparse: incorrect type in argument 1 > >> (different type sizes) @@ expected unsigned short [usertype] *name @@ > >> got ype] *name @@ > >> arch/x86/xen/efi.c:143:35: expected unsigned short [usertype] *name > >> arch/x86/xen/efi.c:143:35: got char *<noident> > >> arch/x86/xen/efi.c:154:35: sparse: incorrect type in argument 1 > >> (different type sizes) @@ expected unsigned short [usertype] *name @@ > >> got ype] *name @@ > >> arch/x86/xen/efi.c:154:35: expected unsigned short [usertype] *name > >> arch/x86/xen/efi.c:154:35: got char *<noident> > > > > Ugh... It looks that compiler does not like L"SecureBoot". > > I have to use this cryptic form from > > drivers/firmware/efi/libstub/secureboot.c... :-((( > > I will send the fix for this tomorrow. > > > > Please ignore: this is sparse, not gcc. You could report it with the sparse > project if you want.
OK, I will ignore that. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
