All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: kernel-build-reports@lists.linaro.org
Cc: Olof's autobuilder <build@lixom.net>,
	olof@lixom.net, Archit Taneja <architt@codeaurora.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org
Subject: Re: next build: 7 warnings 3 failures (next/next-20160708)
Date: Fri, 08 Jul 2016 12:12:09 +0200	[thread overview]
Message-ID: <1706958.r8KHTqFcd9@wuerfel> (raw)
In-Reply-To: <577f78d9.c309620a.24a3d.5ceb@mx.google.com>

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

       reply	other threads:[~2016-07-08 10:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <577f78d9.c309620a.24a3d.5ceb@mx.google.com>
2016-07-08 10:12 ` Arnd Bergmann [this message]
2016-07-08 10:47   ` next build: 7 warnings 3 failures (next/next-20160708) Archit Taneja

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1706958.r8KHTqFcd9@wuerfel \
    --to=arnd@arndb.de \
    --cc=architt@codeaurora.org \
    --cc=build@lixom.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.