On Wed, Jan 27, 2016 at 10:11:47AM +0100, Arnd Bergmann wrote: > On Wednesday 27 January 2016 16:37:45 Fengguang Wu wrote: > > > > Thank you for the tips! I've updated the lists accordingly. > > > > 1st priority > > ============ > > > > arm-allmodconfig > > arm-allnoconfig > > arm-at91_dt_defconfig > > arm-efm32_defconfig > > arm-exynos_defconfig > > arm-multi_v7_defconfig > > arm-multi_v8_defconfig > > arm-shmobile_defconfig > > arm-sunxi_defconfig > > > > 2nd priority > > ============ > > > > arm-arm5 > > arm-arm67 > > arm-imx_v6_v7_defconfig > > arm-ixp4xx_defconfig > > arm-mvebu_v7_defconfig > > arm-omap2plus_defconfig > > arm-sa1100 > > arm-samsung > > arm-sh > > arm-tegra_defconfig > > > > 3nd priority > > ============ > > > > arch/*/configs/* > > Looks good, I'm just unsure about "multi_v8_defconfig", this does not > exist. Do you mean multi_v5_defconfig?
Ah yes, multi_v8_defconfig does not exist actually. > I also wonder if you include 'randconfig' builds for some architectures. > I have patches for all remaining errors and warnings that I see with > ARM randconfig builds today. Not all of them are merged yet, but I could > probably come up with a file to be used as input to KCONFIG_ALLCONFIG > to eliminate the known-broken configurations, if you are interested. If the are mostly ready for upstream, it may be easier to wait until upstream randconfig works just fine for ARM. Thanks, Fengguang
