From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Xiong Zhou <jencce.kernel@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [patch v2] sound/soc/codecs : fix build failure for next-20130325
Date: Wed, 27 Mar 2013 22:57:16 +0000 [thread overview]
Message-ID: <20130327225716.GZ18316@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <51533AD3.9040809@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 359 bytes --]
On Wed, Mar 27, 2013 at 11:30:43AM -0700, Randy Dunlap wrote:
> Do you have a suggestion for a kernel config where SND_SOC_ARIZONA
> is not enabled but SND_SOC_WM_ADSP is enabled, which causes a build
> error in linux-next?
Yes, as I've said several times now the user probably needs to be
conditional. Take a look at what the code is trying to do here...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-03-27 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 13:31 [patch v2] sound/soc/codecs : fix build failure for next-20130325 Xiong Zhou
2013-03-27 13:39 ` Mark Brown
2013-03-27 18:30 ` Randy Dunlap
2013-03-27 22:57 ` 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=20130327225716.GZ18316@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=jencce.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).