From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Lucas Stach <l.stach@pengutronix•de>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Philipp Zabel <p.zabel@pengutronix•de>
Subject: linux-next: build failure after merge of the imx-drm tree
Date: Fri, 18 Jan 2019 14:19:12 +1100 [thread overview]
Message-ID: <20190118141912.69d2a6e9@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
Hi Lucas,
After merging the imx-drm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpu/drm/imx/imx-tve.c: At top level:
drivers/gpu/drm/imx/imx-tve.c:437:29: error: storage size of 'clk_tve_di_ops' isn't known
static const struct clk_ops clk_tve_di_ops = {
^~~~~~~~~~~~~~
Exposed by commit
97144d12df00 ("drm/imx: Allow building under COMPILE_TEST")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-01-18 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 3:19 Stephen Rothwell [this message]
2019-01-18 10:41 ` linux-next: build failure after merge of the imx-drm tree Philipp Zabel
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=20190118141912.69d2a6e9@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=l.stach@pengutronix$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=p.zabel@pengutronix$(echo .)de \
/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