From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Xiong Zhou <jencce.kernel@gmail.com>
Subject: Re: [PATCH -next] sound/soc/codecs: Mark snd-soc-wm2200 and snd-soc-wm-adsp as BROKEN
Date: Fri, 29 Mar 2013 18:50:04 +0000 [thread overview]
Message-ID: <20130329185004.GL18316@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1364582754.3559.66.camel@thor.lan>
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
On Fri, Mar 29, 2013 at 02:45:54PM -0400, Peter Hurley wrote:
> This is stock Ubuntu configs.
Then the stock Ubuntu configuration is not a sensible one, enabling
SND_SOC_ALL_CODECS for any purpose other than build coverage testing is
just a waste of time - that's all it does.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-29 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 14:12 [PATCH -next] sound/soc/codecs: Mark snd-soc-wm2200 and snd-soc-wm-adsp as BROKEN Peter Hurley
2013-03-29 17:12 ` Mark Brown
2013-03-29 18:45 ` Peter Hurley
2013-03-29 18:50 ` Mark Brown [this message]
2013-03-30 12:30 ` Xiong Zhou
2013-03-30 13:52 ` 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=20130329185004.GL18316@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=jencce.kernel@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--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).