From: Michael Ellerman <mpe@ellerman.id.au>
To: Mark Brown <broonie@kernel.org>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Annaliese McDermond <nh6z@nh6z.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: linux-next: build failure after merge of the sound-asoc tree
Date: Wed, 27 Mar 2019 15:29:55 +1100 [thread overview]
Message-ID: <87pnqdndmk.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20190326131550.GB10898@sirena.org.uk>
Mark Brown <broonie@kernel.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
next parent reply other threads:[~2019-03-27 4:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190326133349.3d9427dc@canb.auug.org.au>
[not found] ` <20190326131550.GB10898@sirena.org.uk>
2019-03-27 4:29 ` Michael Ellerman [this message]
2019-03-27 11:57 ` linux-next: build failure after merge of the sound-asoc tree Mark Brown
2019-04-01 11:11 ` Michael Ellerman
2019-04-02 5:14 ` 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=87pnqdndmk.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nh6z@nh6z.net \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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