From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: alsa-devel@alsa-project.org, Stephen Warren <swarren@nvidia.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH V2 1/3] ASoC: tegra: add tegra30-ahub driver
Date: Fri, 13 Apr 2012 17:09:08 +0100 [thread overview]
Message-ID: <20120413160908.GY3168@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F884C29.9060307@wwwdotorg.org>
[-- Attachment #1.1: Type: text/plain, Size: 483 bytes --]
On Fri, Apr 13, 2012 at 09:54:17AM -0600, Stephen Warren wrote:
> BTW, you'll notice that the AHUB driver uses the same REG_IN_ARRAY macro
> as I used in the Tegra20 DAS driver's regmap rework earlier. I'd like to
> just use the same macro in both places for consistency. Are you OK with
> the DAS driver based on that, or do you still want me to rework the
> macro in the DAS driver since the use-case is a little simpler there?
I'd prefer to see the DAS driver reworked I think.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-04-13 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 22:31 [PATCH V2 1/3] ASoC: tegra: add tegra30-ahub driver Stephen Warren
2012-04-10 22:32 ` [PATCH V2 2/3] ASoC: tegra: add tegra30-i2s driver Stephen Warren
2012-04-10 22:32 ` [PATCH V2 3/3] ASoC: tegra: add Kconfig and Makefile support for Tegra30 Stephen Warren
2012-04-13 10:17 ` [PATCH V2 1/3] ASoC: tegra: add tegra30-ahub driver Mark Brown
2012-04-13 15:54 ` Stephen Warren
2012-04-13 16:09 ` 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=20120413160908.GY3168@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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).