From: Rhyland Klein <rklein@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@ti.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Peter Hsiang <cdefgab1288@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: max98095: add jack detection
Date: Tue, 13 Mar 2012 15:18:17 -0700 [thread overview]
Message-ID: <1331677097.9410.8.camel@rklein-linux> (raw)
In-Reply-To: <20120313221235.GJ3177@opensource.wolfsonmicro.com>
On Tue, 2012-03-13 at 15:12 -0700, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Mar 13, 2012 at 12:44:08PM -0700, Rhyland Klein wrote:
> > This change adds the logic to support using the jack detect mechanism built
> > in to the codec to detect both when a jack was inserted and what type of
> > jack is present.
>
> You send another identically titled patch of roughly the same size a
> few minutes ago - what's the difference between the two or is it just a
> resend?
Sorry, they are the same. I hadn't subscribed to the alsa-devel mailing
list and so the first one I sent got as non-subscriber sent email. I
canceled the outstanding notice waiting for approval, and resent once I
subscribed to the mailing list.
-rhyland
>
> * Unknown Key
> * 0x6E30FDDD
next prev parent reply other threads:[~2012-03-13 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 19:44 [PATCH] ASoC: max98095: add jack detection Rhyland Klein
2012-03-13 22:12 ` Mark Brown
2012-03-13 22:18 ` Rhyland Klein [this message]
2012-03-13 23:09 ` Mark Brown
2012-03-13 23:15 ` Rhyland Klein
-- strict thread matches above, loose matches on Subject: below --
2012-03-13 19:40 Rhyland Klein
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=1331677097.9410.8.camel@rklein-linux \
--to=rklein@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cdefgab1288@gmail.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