From: Johan Hedberg <johan.hedberg@gmail.com>
To: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2012-01-03
Date: Mon, 23 Jan 2012 14:56:55 +0200 [thread overview]
Message-ID: <20120123125655.GA20973@x220.ger.corp.intel.com> (raw)
In-Reply-To: <20120103033320.GG1472@joana>
Hi John,
On Tue, Jan 03, 2012, Gustavo Padovan wrote:
> A couple of fixes for the 3.3 release. The majority of the fixes are related
> to the change from tasklets to workqueue in the Bluetooth Core. The rest are
> important fixes over the tree. Exception is "Bluetooth: Rename extfeatures¨,
> as the name says it is just a rename and no harm, but it is a preparation for
> a following fix.
>
> Please pull, or let me know any concerns you have!
>
> Gustavo
>
> --
> The following changes since commit dc0d633e35643662f27a0b1c531da3cd6b204b9c:
>
> Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next (2012-01-02 16:43:54 -0500)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next master
>
> Andre Guedes (5):
> Bluetooth: Rename extfeatures
> Bluetooth: Fix hci_cc_read_local_ext_features()
> Bluetooth: Fix adv_work delay
> Bluetooth: Queue adv_work on system workqueue
> Bluetooth: Fix mgmt_stop_discovery_failed()
>
> Andrei Emeltchenko (1):
> Bluetooth: Correct packet len calculation
>
> Gustavo F. Padovan (8):
> Bluetooth: Fix bacpy in l2cap_core.c
> Bluetooth: Fix context in rfcomm_sock_lock
> Bluetooth: Fix context in RFCOMM tty
> Bluetooth: Remove *_bh locks from SCO
> Bluetooth: Remove local_bh_disable() from hci_sock.c
> Bluetooth: Remove *_bh from socket list lock.
> Bluetooth: Don't use *_bh locks anymore
> Bluetooth: Keep chan->state and sk->sk_state in sync
>
> include/net/bluetooth/hci_core.h | 4 ++--
> net/bluetooth/af_bluetooth.c | 8 ++++----
> net/bluetooth/hci_event.c | 22 +++++++++++++---------
> net/bluetooth/hci_sock.c | 2 --
> net/bluetooth/l2cap_core.c | 26 +++++++++++++-------------
> net/bluetooth/l2cap_sock.c | 2 ++
> net/bluetooth/mgmt.c | 4 ++--
> net/bluetooth/rfcomm/sock.c | 12 ++++++------
> net/bluetooth/rfcomm/tty.c | 22 +++++++++++-----------
> net/bluetooth/sco.c | 8 ++++----
> 10 files changed, 57 insertions(+), 53 deletions(-)
> --
Are you planing to pull this? I've been waiting for that before making
any new pull requests from my (temporary) bluetooth-next tree[1]. If
that's not gonna happen I'll go ahead rebase my tree against latest
wireless-next (including these patches and all other ones that Marcel
has acked since Gustavo started his break), and make a new pull request
to you in the near future.
Johan
[1] http://git.kernel.org/?p=linux/kernel/git/jh/bluetooth-next.git;a=summary
next prev parent reply other threads:[~2012-01-23 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 3:33 pull request: bluetooth-next 2012-01-03 Gustavo Padovan
2012-01-23 12:56 ` Johan Hedberg [this message]
2012-01-23 15:10 ` John W. Linville
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=20120123125655.GA20973@x220.ger.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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 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).