From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Ola Lilja <ola.o.lilja@stericsson.com>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Linus Walleij <linus.walleij@linaro.org>,
kernel-janitors@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [patch] ASoC: Ux500: unlock on an error path
Date: Sun, 17 Jun 2012 20:49:03 +0100 [thread overview]
Message-ID: <20120617194903.GF4267@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120616131927.GB17980@elgon.mountain>
[-- Attachment #1.1: Type: text/plain, Size: 171 bytes --]
On Sat, Jun 16, 2012 at 04:19:27PM +0300, Dan Carpenter wrote:
> There is a missing mutex_unlock() here. The cleanup path also has more
> debug output.
Applied, thanks.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-06-17 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 13:19 [patch] ASoC: Ux500: unlock on an error path Dan Carpenter
2012-06-17 19:49 ` 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=20120617194903.GF4267@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=lrg@ti.com \
--cc=ola.o.lilja@stericsson.com \
--cc=tiwai@suse.de \
/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