From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: S3C64XX: Slow down mic detection rate for wm5102
Date: Fri, 22 Feb 2013 12:10:07 +0000 [thread overview]
Message-ID: <20130222121007.GB19796@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1361534564-2082-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Fri, Feb 22, 2013 at 12:02:44PM +0000, Charles Keepax wrote:
> switch: arizona: Support microphone detection rate configuration
> commit 2e033db5ddf299de2ae568919d78b0258a5a6423
The commit ID is correct there, the commit log is (as you'd expect)
extcon:
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130222/07f03720/attachment.sig>
next prev parent reply other threads:[~2013-02-22 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 12:02 [PATCH] ARM: S3C64XX: Slow down mic detection rate for wm5102 Charles Keepax
2013-02-22 12:10 ` Mark Brown [this message]
2013-03-11 1:31 ` Kukjin Kim
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=20130222121007.GB19796@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).