From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, lars@metafoo.de,
lgirdwood@gmail.com, dan.carpenter@oracle.com,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: dapm: Add missing mutex unlock
Date: Fri, 8 May 2015 11:24:28 +0100 [thread overview]
Message-ID: <20150508102428.GY22845@sirena.org.uk> (raw)
In-Reply-To: <1431078610-4150-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
[-- Attachment #1.1: Type: text/plain, Size: 308 bytes --]
On Fri, May 08, 2015 at 10:50:10AM +0100, Charles Keepax wrote:
> The is a missing mutex unlock on the error path in
> snd_soc_dapm_get_enum_double. This was introduced in commit
> 561ed680b764 ("ASoC: dapm: Add support for autodisable mux controls").
> This patch adds the missing unlock.
Applied, thanks.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-05-08 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 9:50 [PATCH] ASoC: dapm: Add missing mutex unlock Charles Keepax
2015-05-08 10:24 ` 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=20150508102428.GY22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=dan.carpenter@oracle.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.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