From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [patch] ASoC: dapm: release lock on error paths
Date: Sun, 15 Apr 2012 10:47:21 +0100 [thread overview]
Message-ID: <20120415094721.GA3806@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120413192543.GC18505@elgon.mountain>
[-- Attachment #1.1: Type: text/plain, Size: 194 bytes --]
On Fri, Apr 13, 2012 at 10:25:43PM +0300, Dan Carpenter wrote:
> We added locking here but there were a couple error paths where we
> forgot to drop the lock before returning.
Applied, thanks.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [patch] ASoC: dapm: release lock on error paths
Date: Sun, 15 Apr 2012 09:47:21 +0000 [thread overview]
Message-ID: <20120415094721.GA3806@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120413192543.GC18505@elgon.mountain>
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
On Fri, Apr 13, 2012 at 10:25:43PM +0300, Dan Carpenter wrote:
> We added locking here but there were a couple error paths where we
> forgot to drop the lock before returning.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-15 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 19:25 [patch] ASoC: dapm: release lock on error paths Dan Carpenter
2012-04-13 19:25 ` Dan Carpenter
2012-04-15 9:47 ` Mark Brown [this message]
2012-04-15 9:47 ` Mark Brown
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=20120415094721.GA3806@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=lrg@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.