From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Mark Brown <broonie@kernel.org>
Cc: Alexey Brodkin <abrodkin@synopsys.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: next-20160330 build: 1 failures 7 warnings (next-20160330)
Date: Wed, 30 Mar 2016 19:47:42 +0200 [thread overview]
Message-ID: <20160330194742.57866ab6@bbrezillon> (raw)
In-Reply-To: <20160330163545.GF2350@sirena.org.uk>
Hi Mark,
On Wed, 30 Mar 2016 09:35:45 -0700
Mark Brown <broonie@kernel.org> wrote:
> On Wed, Mar 30, 2016 at 07:57:19AM +0100, Build bot for Mark Brown wrote:
>
> Today's -next fails to build an arm allmodconfig due to:
>
> > arm-allmodconfig
> > ../drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c:618:2: error: implicit declaration of function 'drm_connector_unplug_all' [-Werror=implicit-function-declaration]
>
> which appears to be triggered by a missed update in 6c87e5c3ec6db0 (drm:
> Rename drm_connector_unplug_all() to drm_connector_unregister_all())
> due to this driver being newly added in a different tree.
Daniel already fixed it here [1].
[1]http://www.spinics.net/lists/dri-devel/msg103521.html
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-30 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 6:57 next-20160330 build: 1 failures 7 warnings (next-20160330) Build bot for Mark Brown
2016-03-30 16:35 ` Mark Brown
2016-03-30 17:47 ` Boris Brezillon [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=20160330194742.57866ab6@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=abrodkin@synopsys.com \
--cc=airlied@linux.ie \
--cc=broonie@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--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