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: Tue, 2 Apr 2019 12:14:07 +0700 [thread overview]
Message-ID: <20190402051407.GX2059@sirena.org.uk> (raw)
In-Reply-To: <87tvfiou8f.fsf@concordia.ellerman.id.au>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On Mon, Apr 01, 2019 at 10:11:44PM +1100, Michael Ellerman wrote:
> Anyway I think what you've done in next, make the code depend on
> COMMON_CLOCK, is the best option. If anyone cares about that driver on
> powerpc platforms that don't support COMMON_CLOCK they should speak up.
It's probably fine for now for this one driver but it's going to cause
issues going forwards since we're trying to make the framework's clock
handling more standard.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-04-02 5:16 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
2019-04-01 11:11 ` Michael Ellerman
2019-04-02 5:14 ` Mark Brown [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=20190402051407.GX2059@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