From: Mark Brown <broonie@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 11:57:45 +0000 [thread overview]
Message-ID: <20190327115745.GA11404@sirena.org.uk> (raw)
In-Reply-To: <87pnqdndmk.fsf@concordia.ellerman.id.au>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
On Wed, Mar 27, 2019 at 03:29:55PM +1100, Michael Ellerman wrote:
> Mark Brown <broonie@kernel.org> writes:
> > 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?
It's what's in drivers/clk - you'd have to provide clock drivers for all
the clocks that are current supported by arch-specific code, make sure
that those drivers can be instantiated and then remove the custom
implementation of the clock API in arch/powerpc in favour of those.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-03-27 12:22 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 ` linux-next: build failure after merge of the sound-asoc tree Michael Ellerman
2019-03-27 11:57 ` Mark Brown [this message]
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=20190327115745.GA11404@sirena.org.uk \
--to=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=mpe@ellerman.id.au \
--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