From: Philipp Zabel <p.zabel@pengutronix•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
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>
Subject: Re: linux-next: build failure after merge of the imx-drm tree
Date: Fri, 18 Jan 2019 11:41:30 +0100 [thread overview]
Message-ID: <1547808090.3375.5.camel@pengutronix.de> (raw)
In-Reply-To: <20190118141912.69d2a6e9@canb.auug.org.au>
On Fri, 2019-01-18 at 14:19 +1100, Stephen Rothwell wrote:
> 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.
Sorry, I have dropped the commit for now.
regards
Philipp
prev parent reply other threads:[~2019-01-18 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 3:19 linux-next: build failure after merge of the imx-drm tree Stephen Rothwell
2019-01-18 10:41 ` Philipp Zabel [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=1547808090.3375.5.camel@pengutronix.de \
--to=p.zabel@pengutronix$(echo .)de \
--cc=l.stach@pengutronix$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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