From: Daniel Vetter <daniel@ffwll.ch>
To: Mark Brown <broonie@kernel.org>
Cc: Jonathan Liu <net147@gmail.com>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
kernel-build-reports@lists.linaro.org,
Maxime Ripard <maxime.ripard@bootlin.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Chen-Yu Tsai <wens@csie.org>,
linux-next <linux-next@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: next-20180911 build: 1 failures 15 warnings (next-20180911)
Date: Tue, 11 Sep 2018 22:18:01 +0200 [thread overview]
Message-ID: <CAKMK7uF-kF1pBQu-F2tG8vpzw=2nbzO0h1WqhG=WjK7nkdvZfQ@mail.gmail.com> (raw)
In-Reply-To: <20180911201027.GI10123@sirena.org.uk>
On Tue, Sep 11, 2018 at 10:10 PM, Mark Brown <broonie@kernel.org> wrote:
> On Tue, Sep 11, 2018 at 08:47:28PM +0100, Build bot for Mark Brown wrote:
>
> Today's -next fails to build an arm64 defconfig due to:
>
>> arm64-defconfig
>> ERROR: "sun8i_tcon_top_de_config" [drivers/gpu/drm/sun4i/sun4i-tcon.ko] undefined!
>> ERROR: "sun8i_tcon_top_set_hdmi_src" [drivers/gpu/drm/sun4i/sun4i-tcon.ko] undefined!
>> ERROR: "sun8i_tcon_top_of_table" [drivers/gpu/drm/sun4i/sun4i-tcon.ko] undefined!
>
> DRM_SUN4I unconditionally uses these symbols which are only defined when
> DRM_SUN8I_TOP is enabled, not sure what the exact cause is but there's a
> few recent patches to that driver from Jonathan and Chen-Yu so CCing for
> that. I've been missing arm64 builds for a little while so this
> could've been there before today.
Patch seems to have been stuck on dri-devel. I smashed an r-b onto it
so Maxime can apply. Plus a mild rant about Kconfig combinatorial
explosion and whether that's really, really worth all the trouble it's
causing, because I couldn't help myself :-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - 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:[~2018-09-11 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1fzodE-000398-4K@optimist>
2018-09-11 20:10 ` next-20180911 build: 1 failures 15 warnings (next-20180911) Mark Brown
2018-09-11 20:18 ` Daniel Vetter [this message]
2018-09-12 14:02 ` Maxime Ripard
2018-09-12 14:32 ` 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='CAKMK7uF-kF1pBQu-F2tG8vpzw=2nbzO0h1WqhG=WjK7nkdvZfQ@mail.gmail.com' \
--to=daniel@ffwll.ch \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=net147@gmail.com \
--cc=wens@csie.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).