On Wed, Jun 3, 2015 at 9:06 AM, Build bot for Mark Brown broonie@kernel.org wrote:
Tree/Branch: next-20150603 Git describe: next-20150603 Commit: 273de33838 Add linux-next specific files for 20150603
Build Time: 64 min 44 sec
Passed: 4 / 9 ( 44.44 %) Failed: 5 / 9 ( 55.56 %)
Errors: 10 Warnings: 55 Section Mismatches: 1
Failed defconfigs: arm64-allmodconfig arm-multi_v7_defconfig arm-allmodconfig arm-allnoconfig arm64-defconfig
Errors:
arm64-allmodconfig
../include/linux/device.h:1296:1: error: type defaults to 'int' in declaration of 'module_init' [-Werror=implicit-int] ../include/linux/device.h:1301:1: error: type defaults to 'int' in declaration of 'module_exit' [-Werror=implicit-int] ../include/linux/device.h:1296:1: error: type defaults to 'int' in declaration of 'module_init' [-Werror=implicit-int] ../include/linux/device.h:1301:1: error: type defaults to 'int' in declaration of 'module_exit' [-Werror=implicit-int] ../include/linux/device.h:1296:1: error: type defaults to 'int' in declaration of 'module_init' [-Werror=implicit-int] ../include/linux/device.h:1301:1: error: type defaults to 'int' in declaration of 'module_exit' [-Werror=implicit-int]
I'm pretty sure that the above are just duplicates from the tegra/fuse/fuse-tegra error below.
arm-multi_v7_defconfig
../drivers/clk/sunxi/clk-mod0.c:131:1: error: type defaults to 'int' in declaration of 'module_init' [-Werror=implicit-int] ../drivers/clk/sunxi/clk-mod0.c:131:1: error: type defaults to 'int' in declaration of 'module_exit' [-Werror=implicit-int]
The sunxi should be fixed with this now added:
https://lkml.kernel.org/r/1433358578-9579-1-git-send-email-paul.gortmaker@wi...
../drivers/soc/tegra/fuse/fuse-tegra.c:171:1: error: type defaults to 'int' in declaration of 'module_init' [-Werror=implicit-int] ../drivers/soc/tegra/fuse/fuse-tegra.c:171:1: error: type defaults to 'int' in declaration of 'module_exit' [-Werror=implicit-int]
The tegra fix should ideally be in the tegra tree, as per here:
https://lkml.kernel.org/r/20150603160808.GM29898@windriver.com
...but since I didn't hear from Thierry yet, I put in this preemptive fix, since we get those ugly looking device.h errors above from this.
https://git.kernel.org/cgit/linux/kernel/git/paulg/linux.git/commit/?h=init-...
arm-allmodconfig
../drivers/cpufreq/exynos-cpufreq.c:239:1: error: type defaults to 'int' in declaration of 'device_initcall' [-Werror=implicit-int]
The exynos should be fixed now as well, with this:
https://lkml.kernel.org/r/1433366298-30016-1-git-send-email-paul.gortmaker@w...
../drivers/clk/sunxi/clk-mod0.c:131:1: error: type defaults to 'int' in declaration of 'module_init' [-Werror=implicit-int] ../drivers/clk/sunxi/clk-mod0.c:131:1: error: type defaults to 'int' in declaration of 'module_exit' [-Werror=implicit-int]
The sunxi was covered above.
../drivers/hwtracing/coresight/coresight-replicator-qcom.c:214:1: error: type defaults to 'int' in declaration of 'module_init' [-Werror=implicit-int] ../drivers/hwtracing/coresight/coresight-replicator-qcom.c:214:1: error: type defaults to 'int' in declaration of 'module_exit' [-Werror=implicit-int]
I can't fix this one from my tree since the code only exists in next. But I've passed the fix onto Greg since it comes via his staging tree:
https://lkml.kernel.org/r/1433364777-29651-1-git-send-email-paul.gortmaker@w...
../drivers/soc/tegra/fuse/fuse-tegra.c:171:1: error: type defaults to 'int' in declaration of 'module_init' [-Werror=implicit-int] ../drivers/soc/tegra/fuse/fuse-tegra.c:171:1: error: type defaults to 'int' in declaration of 'module_exit' [-Werror=implicit-int]
Same tegra thing mentioned above.
../drivers/tty/serial/8250/8250_omap.c:586:20: error: redefinition of 'omap8250_irq'
I don't think that one was caused by me..
arm64-defconfig
../include/linux/device.h:1296:1: error: type defaults to 'int' in declaration of 'module_init' [-Werror=implicit-int] ../include/linux/device.h:1301:1: error: type defaults to 'int' in declaration of 'module_exit' [-Werror=implicit-int]
Tegra one again, unfortunately.
Thanks again for the extra build coverage; I should have given a heads-up earlier that I was proactively sorting this out once I saw the results.
I'd run all the ARM defconfigs recently, but forgot to go back and redo the allmodconfigs after test-merging with the latest linux-next. :-/
Paul.