From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rhyland Klein <rklein@nvidia.com>
Cc: Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org, Peter Hsiang <cdefgab1288@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: max98095: add jack detection
Date: Sat, 17 Mar 2012 21:48:08 +0000 [thread overview]
Message-ID: <20120317214808.GH3315@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1331849267-30710-1-git-send-email-rklein@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
On Thu, Mar 15, 2012 at 03:07:47PM -0700, Rhyland Klein wrote:
> v2:
> - Removed useless function for irq_handler
> - removed enable/disable irq
> - Added pdata entry for jack detections slew rate
> - get irq directly from dev
Applied, but always include this stuff after the --- as it shouldn't end
up in git (see SubmittingPatches).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-17 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 22:07 [PATCH v2] ASoC: max98095: add jack detection Rhyland Klein
2012-03-17 21:48 ` 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=20120317214808.GH3315@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=cdefgab1288@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rklein@nvidia.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