From: Johan Hedberg <johan.hedberg@gmail.com>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv3 0/3] Bluetooth: Change socket lock to l2cap_chan lock
Date: Thu, 23 Feb 2012 00:42:56 +0200 [thread overview]
Message-ID: <20120222224256.GA9544@x220.ger.corp.intel.com> (raw)
In-Reply-To: <1329923517-5425-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
On Wed, Feb 22, 2012, Andrei Emeltchenko wrote:
> Changing socket lock to L2CAP chan lock in L2CAP code. Needed for implementing
> protocols above L2CAP without creating sockets.
>
> Changes:
> * PATCHv3: Do not remove couple of empty lines and remove old comments.
> * PATCHv2: Rebase remaining parts against latest tree and merge all
> patches dealing with converting sk lock to chan lock together following
> recommendation from Ulisses and Gustavo.
> * PATCHv1: Added extra line (per Gustavo comment)
> * RFCv6: Same code but patches 2,3 and 4 from RFCv5 are merged together
> following recommendations from review.
> * RFCv5: Fixed locking bug in l2cap_data_channel, added locks in
> l2cap_sock_shutdown function, fixed several styles issues.
> * RFCv4: Better split patches so they looks more clear and obvious,
> taking coments about naming change and delete unused vars. See diff change
> from the previous version below:
> * RFCv3: Split the big patch to several small (I believe logical) chunks,
> remove unneded locks from cleanup_listen, use the same arguments for
> locked/unlocked socket error functions.
> * RFCv2: Convert l2cap channel list back to mutex from RCU list.
>
> Andrei Emeltchenko (3):
> Bluetooth: Add unlocked __l2cap_chan_add function
> Bluetooth: Change sk lock to chan lock in L2CAP core
> Bluetooth: Remove socket lock check
>
> net/bluetooth/l2cap_core.c | 175 ++++++++++++++++++++++++++------------------
> net/bluetooth/l2cap_sock.c | 26 +++++--
> 2 files changed, 125 insertions(+), 76 deletions(-)
All three patches have been applied. Thanks.
Johan
prev parent reply other threads:[~2012-02-22 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 15:11 [PATCHv3 0/3] Bluetooth: Change socket lock to l2cap_chan lock Andrei Emeltchenko
2012-02-22 15:11 ` [PATCHv3 1/3] Bluetooth: Add unlocked __l2cap_chan_add function Andrei Emeltchenko
2012-02-22 15:11 ` [PATCHv3 2/3] Bluetooth: Change sk lock to chan lock in L2CAP core Andrei Emeltchenko
2012-02-22 18:41 ` Gustavo Padovan
2012-02-22 15:11 ` [PATCHv3 3/3] Bluetooth: Remove socket lock check Andrei Emeltchenko
2012-02-22 22:42 ` Johan Hedberg [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=20120222224256.GA9544@x220.ger.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.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;
as well as URLs for NNTP newsgroup(s).