From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: alsa-devel@alsa-project.org, Cliff Cai <cliff.cai@analog.com>,
device-drivers-devel@blackfin.uclinux.org,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [Device-drivers-devel] [PATCH v2] ASoC: add SSM2604 codec driver
Date: Sun, 27 Mar 2011 11:41:16 +0100 [thread overview]
Message-ID: <20110327104116.GB11148@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTim71QcpBTXLC2fFnqqW+SMJnNFpJB9qwn8EzeWv@mail.gmail.com>
On Sun, Mar 27, 2011 at 12:11:54AM -0400, Mike Frysinger wrote:
> On Sat, Mar 26, 2011 at 08:12, Mark Brown wrote:
> > If the device only supports I2C then there's no need for the ifdefs.
> i thought in the past you wanted these things because you wanted to be
> able to build codecs regardless of the bus support (for testing iirc?)
That has never been the case, SND_SOC_ALL_CODECS has always built things
only if there is a bus for them. If you support mulitple busses they
should be conditional so that you only need one of them to build but if
there's only one supported this is not relevant.
prev parent reply other threads:[~2011-03-27 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 5:54 [PATCH] ASoC: add SSM2604 codec driver Mike Frysinger
2010-08-07 12:44 ` Mark Brown
[not found] ` <20100807124416.GB11817-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2010-08-07 15:21 ` Mike Frysinger
2011-03-26 9:07 ` [PATCH v2] " Mike Frysinger
2011-03-26 12:12 ` Mark Brown
2011-03-27 4:11 ` [Device-drivers-devel] " Mike Frysinger
2011-03-27 10:41 ` 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=20110327104116.GB11148@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=cliff.cai@analog.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=lrg@slimlogic.co.uk \
--cc=vapier@gentoo.org \
/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).