From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch -next] iwlwifi: unlock on error path
Date: Thu, 14 Jun 2012 18:38:30 +0000 [thread overview]
Message-ID: <1339699110.9786.9.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120614183526.GD6383@elgon.mountain> (sfid-20120614_203557_447921_E8796EB4)
On Thu, 2012-06-14 at 21:35 +0300, Dan Carpenter wrote:
> We introduced a lock here in ff1ffb850b ("iwlwifi: fix dynamic
> loading"). But we missed an error path which needs an unlock.
Thanks Dan. John, this is the other merge issue I was talking about :-)
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch -next] iwlwifi: unlock on error path
Date: Thu, 14 Jun 2012 20:38:30 +0200 [thread overview]
Message-ID: <1339699110.9786.9.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120614183526.GD6383@elgon.mountain> (sfid-20120614_203557_447921_E8796EB4)
On Thu, 2012-06-14 at 21:35 +0300, Dan Carpenter wrote:
> We introduced a lock here in ff1ffb850b ("iwlwifi: fix dynamic
> loading"). But we missed an error path which needs an unlock.
Thanks Dan. John, this is the other merge issue I was talking about :-)
johannes
next prev parent reply other threads:[~2012-06-14 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 18:35 [patch -next] iwlwifi: unlock on error path Dan Carpenter
2012-06-14 18:35 ` Dan Carpenter
2012-06-14 18:38 ` Johannes Berg [this message]
2012-06-14 18:38 ` Johannes Berg
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=1339699110.9786.9.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dan.carpenter@oracle.com \
--cc=ilw@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=wey-yi.w.guy@intel.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 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.