From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Harsha, Priya" <priya.harsha@intel.com>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/3] ASoC: sn95031: Add jack support in the codec
Date: Wed, 9 Feb 2011 13:07:34 +0000 [thread overview]
Message-ID: <20110209130734.GC24042@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <438BB0150E931F4B9CE701519A4463010846D59CDE@bgsmsx502.gar.corp.intel.com>
On Wed, Feb 09, 2011 at 06:36:44PM +0530, Koul, Vinod wrote:
> > The code itself looks OK.
> In that case would it be okay if you accept this and I will send follow
> patch right away fixing this...Or I will resend all three?
Please wait for the others, I've not reviewed them yet.
next prev parent reply other threads:[~2011-02-09 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 9:12 [PATCH 0/3] add support for jack detection in mid-x86 Koul, Vinod
2011-02-09 9:12 ` [PATCH 1/3] ASoC: sn95031: Add jack support in the codec Koul, Vinod
2011-02-09 12:11 ` Mark Brown
2011-02-09 13:06 ` Koul, Vinod
2011-02-09 13:07 ` Mark Brown [this message]
2011-02-09 9:12 ` [PATCH 2/3] ASoC: mfld_machine: Add support for jack detection Koul, Vinod
2011-02-09 13:55 ` Mark Brown
2011-02-09 14:38 ` Koul, Vinod
2011-02-09 14:39 ` Mark Brown
2011-02-09 14:53 ` Koul, Vinod
2011-02-09 9:12 ` [PATCH 3/3] ASoC: sn95031: Add support for reading mic bias Koul, Vinod
2011-02-09 15:06 ` Mark Brown
2011-02-09 15:09 ` Koul, Vinod
-- strict thread matches above, loose matches on Subject: below --
2011-02-09 16:14 [PATCH 0/3] add support for jack detection in mid-x86 Koul, Vinod
2011-02-09 16:14 ` [PATCH 1/3] ASoC: sn95031: Add jack support in the codec Koul, Vinod
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=20110209130734.GC24042@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=priya.harsha@intel.com \
--cc=vinod.koul@intel.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).