All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Kevin Fang <chienf@qca.qualcomm.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] ath6kl: unlock if ath6kl_cfg80211_connect() fails
Date: Mon, 21 Nov 2011 16:21:47 +0000	[thread overview]
Message-ID: <4ECA7A9B.3070501@qca.qualcomm.com> (raw)
In-Reply-To: <20111118140932.GB9685@elgon.mountain>

On 11/18/2011 04:09 PM, Dan Carpenter wrote:
> There is an unlock missing on this error path.
> 
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>

Thanks, applied to ath6kl.git. There was a conflict but that was easy to
fix.

Kalle

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Kevin Fang <chienf@qca.qualcomm.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	<linux-wireless@vger.kernel.org>,
	<kernel-janitors@vger.kernel.org>
Subject: Re: [patch] ath6kl: unlock if ath6kl_cfg80211_connect() fails
Date: Mon, 21 Nov 2011 18:21:47 +0200	[thread overview]
Message-ID: <4ECA7A9B.3070501@qca.qualcomm.com> (raw)
In-Reply-To: <20111118140932.GB9685@elgon.mountain>

On 11/18/2011 04:09 PM, Dan Carpenter wrote:
> There is an unlock missing on this error path.
> 
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>

Thanks, applied to ath6kl.git. There was a conflict but that was easy to
fix.

Kalle

  reply	other threads:[~2011-11-21 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 14:09 [patch] ath6kl: unlock if ath6kl_cfg80211_connect() fails Dan Carpenter
2011-11-18 14:09 ` Dan Carpenter
2011-11-21 16:21 ` Kalle Valo [this message]
2011-11-21 16:21   ` Kalle Valo

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=4ECA7A9B.3070501@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=chienf@qca.qualcomm.com \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.