From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
"kuninori.morimoto.gx" <kuninori.morimoto.gx@renesas.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
David@alsa-project.org, Chen <david.chen@diasemi.com>,
lrg <lrg@ti.com>
Subject: Re: [PATCH v8 3/3 RESEND] ASoC: da7210: Add support for line input and mic
Date: Thu, 3 Nov 2011 14:08:56 +0530 [thread overview]
Message-ID: <1320309536.20814.4.camel@matrix> (raw)
In-Reply-To: <20111101185520.GK10029@opensource.wolfsonmicro.com>
On Tue, 2011-11-01 at 18:55 +0000, Mark Brown wrote:
> On Tue, Nov 01, 2011 at 06:42:29PM +0530, Ashish Chavan wrote:
> > DA7210 has three line inputs (AUX1 Left, AUX1 Right and AUX2) and
> > a stereo MIC. This patch adds gain controls for MIC, AUX1, AUX2 as
> > well as INPGA.
> >
> > Signed-off-by: Ashish Chavan <ashish.chavan@kpitcummins.com>
> > Signed-off-by: David Dajun Chen <dchen@diasemi.com>
>
> Applied, thanks. When resending patches you should always include any
> acks that were given on previous postings.
>
Oh yes, I missed that.
BTW I still can't see this patch in either for-3.2 or for-3.3 branch of
linux-2.6-asoc.git! Do I need to wait for some time before it appears
there?
Thanks,
-- Ashish (GNU Fan)
next prev parent reply other threads:[~2011-11-03 8:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 13:12 [PATCH v8 3/3 RESEND] ASoC: da7210: Add support for line input and mic Ashish Chavan
2011-11-01 18:55 ` Mark Brown
2011-11-03 8:38 ` Ashish Chavan [this message]
2012-01-02 9:17 ` Ashish Chavan
2012-01-02 11:35 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2012-01-02 12:05 Ashish Chavan
2012-01-02 12:00 ` Mark Brown
2012-01-02 12:16 ` Ashish Chavan
2012-01-02 12:11 ` Mark Brown
2012-01-02 12:40 ` Ashish Chavan
2012-01-02 12:58 ` Mark Brown
2012-01-02 13:25 ` Ashish Chavan
2012-01-02 13:17 ` Mark Brown
2012-01-02 14:08 ` Ashish Chavan
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=1320309536.20814.4.camel@matrix \
--to=ashish.chavan@kpitcummins.com \
--cc=David@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=david.chen@diasemi.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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 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).