[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87pnqdndmk.fsf@concordia.ellerman.id.au>
Date: Wed, 27 Mar 2019 15:29:55 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Mark Brown <broonie@...nel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Liam Girdwood <lgirdwood@...il.com>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Annaliese McDermond <nh6z@...z.net>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>, linuxppc-dev@...abs.org
Subject: Re: linux-next: build failure after merge of the sound-asoc tree
Mark Brown <broonie@...nel.org> writes:
> On Tue, Mar 26, 2019 at 01:33:49PM +1100, Stephen Rothwell wrote:
>
>> After merging the sound-asoc tree, today's linux-next build (powerpc
>> allyesconfig) failed like this:
>
>> sound/soc/codecs/tlv320aic32x4-clk.c: In function 'clk_aic32x4_pll_prepare':
>> include/linux/kernel.h:979:32: error: dereferencing pointer to incomplete type 'struct clk_hw'
>> BUILD_BUG_ON_MSG(!__same_type(*(ptr), ((type *)0)->member) && \
>> ^~~~~~
>
> Hrm, seems PowerPC is still not using the common clock API - is there
> any plan for that? There are some ASoC PowerPC uses so it's going to be
> a bit of an issue as we expand our use of the clock API.
I don't know anything about the common clock API. What would it involve
for powerpc to use it?
cheers
Powered by blists - more mailing lists