On Friday, July 8, 2016 2:56:41 AM CEST Olof's autobuilder wrote: > Here are the build results from automated periodic testing. > > The tree being built was next, found at: > > http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git (master branch) > > Topmost commit: > > a379b037 Add linux-next specific files for 20160708 > > Build logs (stderr only) can be found at the following link (experimental): > > http://arm-soc.lixom.net/buildlogs/next/next-20160708/ > > > Runtime: 114m 2s > > Passed: 117 > Failed: 3 > > Warnings: 7 > > Section mismatches: 0 > > ------------------------------------------------------------------------------- > > Failed defconfigs: > arm64.allmodconfig > arm64.defconfig > arm.allmodconfig > > ------------------------------------------------------------------------------- > > Errors: > > arm64.allmodconfig: > /work/build/batch/drivers/gpu/drm/rockchip/rockchip_drm_drv.c:17:27: fatal error: asm/dma-iommu.h: No such file or directory > > arm64.defconfig: > > arm.allmodconfig: It seems the link errors didn't make it into the log, this is from http://arm-soc.lixom.net/buildlogs/next/next-20160708/buildall.arm.allmodconfig.log.failed and we get the same thing on arm64 defconfig: drivers/gpu/drm/msm/msm_drv.o:(.rodata+0x2c0): multiple definition of `__mod_of__dt_match_device_table' drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.o:(.rodata+0x11c): first defined here The commit causing it is b71a717c955a ("drm/msm/mdp5: Update compatible strings for MDSS/MDP5") and the problem is that two match tables with the same name "dt_match" are linked into the same module. Arnd _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
