linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jonathan Liu <net147@gmail.com>, Chen-Yu Tsai <wens@csie.org>,
	Maxime Ripard <maxime.ripard@bootlin.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	kernel-build-reports@lists.linaro.org
Subject: Re: next-20180911 build: 1 failures 15 warnings (next-20180911)
Date: Tue, 11 Sep 2018 21:10:27 +0100	[thread overview]
Message-ID: <20180911201027.GI10123@sirena.org.uk> (raw)
In-Reply-To: <E1fzodE-000398-4K@optimist>


[-- Attachment #1.1: Type: text/plain, Size: 727 bytes --]

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.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

       reply	other threads:[~2018-09-11 20:10 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 ` Mark Brown [this message]
2018-09-11 20:18   ` next-20180911 build: 1 failures 15 warnings (next-20180911) Daniel Vetter
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=20180911201027.GI10123@sirena.org.uk \
    --to=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).