From: Mark Brown <broonie@kernel•org>
To: James Qian Wang <james.qian.wang@arm•com>,
Liviu Dudau <liviu.dudau@arm•com>,
Brian Starkey <brian.starkey@arm•com>,
David Airlie <airlied@linux•ie>, Daniel Vetter <daniel@ffwll•ch>
Cc: kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
dri-devel@lists•freedesktop.org
Subject: Re: next-20190611 build: 1 failures 20 warnings (next-20190611)
Date: Tue, 11 Jun 2019 17:45:54 +0100 [thread overview]
Message-ID: <20190611164554.GD5316@sirena.org.uk> (raw)
In-Reply-To: <E1haipo-0003Ae-CW@optimist>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
On Tue, Jun 11, 2019 at 04:37:16PM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm allmodconfig due to:
> arm-allmodconfig
> ../drivers/gpu/drm/arm/display/komeda/d71/d71_component.c:206:30: error: passing argument 3 of 'd71_layer_update_fb' from incompatible pointer type [-Werror=incompatible-pointer-types]
> ../drivers/gpu/drm/arm/display/komeda/d71/d71_component.c:385:30: error: passing argument 3 of 'd71_layer_update_fb' from incompatible pointer type [-Werror=incompatible-pointer-types]
due to 75f3b7efacb8e (drm/komeda: Add format support for Y0L2, P010,
YUV420_8/10BIT) which introduces those two calls.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-06-11 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 15:37 next-20190611 build: 1 failures 20 warnings (next-20190611) Build bot for Mark Brown
2019-06-11 16:45 ` Mark Brown [this message]
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=20190611164554.GD5316@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=airlied@linux$(echo .)ie \
--cc=brian.starkey@arm$(echo .)com \
--cc=daniel@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=james.qian.wang@arm$(echo .)com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=liviu.dudau@arm$(echo .)com \
/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