On Tue, Jan 3, 2017 at 3:51 AM, Build bot for Mark Brown <broonie@xxxxxxxxxx> wrote: > Tree/Branch: next-20170103 > Git describe: next-20170103 > Commit: 533d7e3a9f Add linux-next specific files for 20170103 [...] > arm-allmodconfig > ../samples/vfio-mdev/mtty.c:1418:20: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] I got the same on my i386 allmodconfig build today ; unclear why sfr's build didn't barf on the same issue -- gcc version perhaps? Anyway, I posted a fix: https://lkml.kernel.org/r/20170103193643.8631-1-paul.gortmaker@xxxxxxxxxxxxx Paul. -- > > arm64-defconfig > ../arch/arm64/include/asm/setup.h:14:29: error: redefinition of 'kaslr_offset' > ../arch/arm64/include/asm/setup.h:14:29: error: redefinition of 'kaslr_offset' > ../arch/arm64/include/asm/setup.h:14:29: error: redefinition of 'kaslr_offset' > ../arch/arm64/include/asm/setup.h:14:29: error: redefinition of 'kaslr_offset' > ../arch/arm64/include/asm/setup.h:14:29: error: redefinition of 'kaslr_offset' > ../arch/arm64/include/asm/setup.h:14:29: error: redefinition of 'kaslr_offset' > ../arch/arm64/include/asm/setup.h:14:29: error: redefinition of 'kaslr_offset' > > ------------------------------------------------------------------------------- > defconfigs with issues (other than build errors): > 2 warnings 0 mismatches : arm64-allmodconfig > 2 warnings 0 mismatches : arm-allmodconfig > > ------------------------------------------------------------------------------- > > Errors summary: 2 > 24 ../arch/arm64/include/asm/setup.h:14:29: error: redefinition of 'kaslr_offset' > 1 ../samples/vfio-mdev/mtty.c:1418:20: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] > [...] -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
