From: Daniel Vetter <daniel@ffwll.ch>
To: Mark Brown <broonie@kernel.org>
Cc: linaro-kernel@lists.linaro.org,
kernel-build-reports@lists.linaro.org,
dri-devel@lists.freedesktop.org, linux-next@vger.kernel.org,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: next-20160817 build: 2 failures 5 warnings (next-20160817)
Date: Wed, 17 Aug 2016 12:14:53 +0200 [thread overview]
Message-ID: <20160817101453.GT6232@phenom.ffwll.local> (raw)
In-Reply-To: <20160817092644.GE9347@sirena.org.uk>
On Wed, Aug 17, 2016 at 10:26:44AM +0100, Mark Brown wrote:
> On Wed, Aug 17, 2016 at 08:28:17AM +0100, Build bot for Mark Brown wrote:
>
> Today's -next fails to build an arm64 allmodconfig due to:
>
> > arm64-allmodconfig
> > ../drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.c:140:18: error: passing argument 1 of 'dc_ops->cleanup' from incompatible pointer type [-Werror=incompatible-pointer-types]
> > ../drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c:994:52: error: 'dev' undeclared (first use in this function)
> > ../drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c:1055:52: error: 'dev' undeclared (first use in this function)
> > ../drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c:1065:1: error: expected '}' before ';' token
>
> caused by d25bcfb8c2 (drm/hisilicon: Don't set drm_device->platformdev)
> which does a a partial conversion to new APIs.
Yeah I screwed up since I naively assumed that compile testing on arm
32bit multiarch is good enough. I'm setting up an arm64 environment now,
but would be nice if arm folks would stop loving bazillions of configs so
much ;-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-17 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 7:28 next-20160817 build: 2 failures 5 warnings (next-20160817) Build bot for Mark Brown
2016-08-17 9:26 ` Mark Brown
2016-08-17 10:14 ` Daniel Vetter [this message]
2016-08-17 10:45 ` Mark Brown
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=20160817101453.GT6232@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=broonie@kernel.org \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).