From: Greg KH <greg@kroah.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [2.6.38-rc6, patch] fix hci_dev_list locking...
Date: Tue, 1 Mar 2011 10:49:19 -0500 [thread overview]
Message-ID: <20110301154919.GB27312@kroah.com> (raw)
In-Reply-To: <AANLkTi=_gAQiAqKsYa2=Haq0ceJwK3n7OafDk6Lb7MZE@mail.gmail.com>
On Tue, Mar 01, 2011 at 11:41:38PM +0800, Daniel J Blueman wrote:
> Release acquired lock on error path, fixing potential hang up.
>
> Signed-off-by: Daniel J Blueman <daniel.blueman@gmail.com>
>
> diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c
> index f827fd9..ace8726 100644
Please go read Documentation/stable_kernel_rules.txt for how to properly
submit patches to the stable kernel tree (hint, this way was not
correct...)
thanks,
greg k-h
next prev parent reply other threads:[~2011-03-01 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 15:41 [2.6.38-rc6, patch] fix hci_dev_list locking Daniel J Blueman
2011-03-01 15:49 ` Greg KH [this message]
2011-03-01 15:53 ` [stable] " Daniel J Blueman
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=20110301154919.GB27312@kroah.com \
--to=greg@kroah.com \
--cc=daniel.blueman@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=stable@kernel.org \
/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