From: Mark Brown <broonie@sirena.org.uk>
To: Troy Kisky <troy.kisky@boundarydevices.com>
Cc: alsa-devel@alsa-project.org, Arun KS <arunks@mistralsolutions.com>
Subject: Re: [PATCH 0/5] [RFC] ALSA ASoC Support for TLVaic23b audio codec
Date: Mon, 29 Sep 2008 18:32:03 +0100 [thread overview]
Message-ID: <20080929173202.GA18699@sirena.org.uk> (raw)
In-Reply-To: <48E10ABE.5030703@boundarydevices.com>
On Mon, Sep 29, 2008 at 10:05:02AM -0700, Troy Kisky wrote:
> Mark Brown wrote:
> > No, the I2C and SPI support should both be part of the driver. The
> Seems to me a Kconfig option would be more efficient. Otherwise, one of the
> two options is just going to waste space.
We need to support building for both I2C and SPI simultaneously in order
to allow kernels supporting multiple boards to be built. If the
selection is done at build time then the number of configurations that
can be built in a single image is restricted needlessly.
I'd ack patches which made it possible to configure one or the other out
but given the tiny amount of glue required I'd personally not bother
writing that.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
next prev parent reply other threads:[~2008-09-29 17:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 9:41 [PATCH 0/5] [RFC] ALSA ASoC Support for TLVaic23b audio codec Arun KS
2008-09-29 16:47 ` Troy Kisky
2008-09-29 16:54 ` Mark Brown
2008-09-29 17:05 ` Troy Kisky
2008-09-29 17:32 ` Mark Brown [this message]
2008-09-29 17:27 ` Troy Kisky
2008-09-29 17:39 ` Mark Brown
2008-09-29 17:58 ` Troy Kisky
2008-09-29 18:30 ` Mark Brown
2008-09-29 19:07 ` Troy Kisky
2008-09-29 19:50 ` Mark Brown
2008-09-29 21:15 ` Troy Kisky
-- strict thread matches above, loose matches on Subject: below --
2008-09-29 9:41 Arun KS
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=20080929173202.GA18699@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=arunks@mistralsolutions.com \
--cc=troy.kisky@boundarydevices.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.