From: Mark Brown <broonie@kernel•org>
To: Daniel Vetter <daniel.vetter@ffwll•ch>,
Chris Wilson <chris@chris-wilson•co.uk>,
Dave Airlie <airlied@redhat•com>, Jie Qiu <jie.qiu@mediatek•com>,
CK Hu <ck.hu@mediatek•com>
Cc: kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
dri-devel@lists•freedesktop.org
Subject: Re: next-20160518 build: 2 failures 20 warnings (next-20160518)
Date: Wed, 18 May 2016 11:15:59 +0100 [thread overview]
Message-ID: <20160518101559.GJ8104@sirena.org.uk> (raw)
In-Reply-To: <E1b2vXq-0003Ij-Ek@optimist>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On Wed, May 18, 2016 at 08:05:26AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build arm and arm64 allmodconfigs fail to build
due to:
> arm64-allmodconfig
> arm-allmodconfig
> ../drivers/gpu/drm/mediatek/mtk_drm_fb.c:141:30: error: passing argument 1 of 'drm_gem_object_lookup' from incompatible pointer type [-Werror=incompatible-pointer-types]
> ../drivers/gpu/drm/mediatek/mtk_drm_fb.c:141:8: error: too many arguments to function 'drm_gem_object_lookup'
> ../drivers/gpu/drm/mediatek/mtk_drm_gem.c:142:30: error: passing argument 1 of 'drm_gem_object_lookup' from incompatible pointer type [-Werror=incompatible-pointer-types]
> ../drivers/gpu/drm/mediatek/mtk_drm_gem.c:142:8: error: too many arguments to function 'drm_gem_object_lookup'
Apparently triggered by 8ad0bd84f98607 (drm: Remove unused drm_device
from drm_gem_object_lookup()) which didn't update the Mediatek drivers.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-18 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 7:05 next-20160518 build: 2 failures 20 warnings (next-20160518) Build bot for Mark Brown
2016-05-18 10:15 ` Mark Brown [this message]
2016-05-18 10:23 ` Chris Wilson
2016-05-19 0:00 ` Stephen Rothwell
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=20160518101559.GJ8104@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=airlied@redhat$(echo .)com \
--cc=chris@chris-wilson$(echo .)co.uk \
--cc=ck.hu@mediatek$(echo .)com \
--cc=daniel.vetter@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=jie.qiu@mediatek$(echo .)com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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