From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 0/3] ASoC: twl4030/tpa6130a2:?DB_RANGE mapping fixes
Date: Mon, 19 Jul 2010 11:30:38 +0100 [thread overview]
Message-ID: <20100719103038.GA9203@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <201007191214.50115.peter.ujfalusi@nokia.com>
On Mon, Jul 19, 2010 at 12:14:49PM +0300, Peter Ujfalusi wrote:
> I see, but I still don't see problem with this:
Meh, that works but I guess my brain can't imagine concepts that ugly :)
> With the patches I have sent for alsa-lib both A and B style of array going to
> be handled correctly.
> If you have time, can you take a look at them?
I had a look, I don't really have much to say - they look like they do
the job.
next prev parent reply other threads:[~2010-07-19 10:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 10:17 [PATCH 0/3] ASoC: twl4030/tpa6130a2: DB_RANGE mapping fixes Peter Ujfalusi
2010-07-16 10:17 ` [PATCH 1/3] ASoC: TWL4030: Fix DB_RANGE tlv mapping for digital loopback Peter Ujfalusi
2010-07-16 10:17 ` [PATCH 2/3] ASoC: tpa6130a2: Fix DB_RANGE mapping for tpa6130a2 chip Peter Ujfalusi
2010-07-16 10:17 ` [PATCH 3/3] ASoC: tpa6130a2: Fix DB_RANGE mapping for tpa6140a2 chip Peter Ujfalusi
2010-07-16 10:24 ` [PATCH 0/3] ASoC: twl4030/tpa6130a2: DB_RANGE mapping fixes Mark Brown
2010-07-16 11:05 ` Peter Ujfalusi
2010-07-16 12:33 ` [PATCH 0/3] ASoC: twl4030/tpa6130a2:?DB_RANGE " Mark Brown
2010-07-19 5:57 ` Peter Ujfalusi
2010-07-19 8:51 ` Mark Brown
2010-07-19 9:14 ` Peter Ujfalusi
2010-07-19 10:30 ` Mark Brown [this message]
2010-07-19 10:32 ` Peter Ujfalusi
2010-07-19 10:43 ` Peter Ujfalusi
2010-07-19 16:25 ` Takashi Iwai
2010-07-20 5:39 ` Peter Ujfalusi
2010-07-20 5:42 ` Takashi Iwai
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=20100719103038.GA9203@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.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.