From: Gustavo Padovan <padovan@profusion.mobi>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: pull request: bluetooth-next 2011-12-27
Date: Tue, 27 Dec 2011 14:21:03 -0200 [thread overview]
Message-ID: <20111227162103.GB8298@joana> (raw)
Hi John,
This is my last pull request to 3.3. A good part of the changes here are still
related to the workqueue changes, they are both by me and Ulisses Furquim.
Besides that there are more AMP work from Andrei and SMP work from Brian Gix
plus some other fix/improvements.
Please pull.
Gustavo
The following changes since commit 27bf88829f50cf1af2b052ecee2f6f0dbe4a5141:
mac80211: Fixing sparse warning at sta_info.c (2011-12-19 15:06:09 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next master
Andrei Emeltchenko (5):
Bluetooth: Split ctrl init to BREDR and AMP parts
Bluetooth: Initialize default flow control mode
Bluetooth: Check for flow control mode
Bluetooth: Clean up magic pointers
Bluetooth: Remove magic numbers from le scan cmd
Bing Zhao (1):
Bluetooth: btusb: fix bInterval for high/super speed isochronous endpoints
Brian Gix (2):
Bluetooth: Add MITM mechanism to LE-SMP
Bluetooth: Add SMP to User Passkey and Confirm
Gustavo F. Padovan (9):
Bluetooth: Move l2cap_{set,clear}_timer to l2cap.h
Bluetooth: convert security timer to delayed_work
Bluetooth: Rename info_work to info_timer
Bluetooth: fix bt_accept_dequeue() to work in process context
Bluetooth: Remove l2cap priority from inside RFCOMM.
Bluetooth: add debug output to l2cap_ack_timeout()
Bluetooth: Remove lock from inquiry_cache
Bluetooth: remove *_bh usage from hci_dev_list and hci_cb_list
Bluetooth: Don't disable interrupt when locking the queue
Hemant Gupta (1):
Bluetooth: Incorrect address while storing LTK.
Jesse Sung (1):
Bluetooth: Add support for BCM20702A0 [0a5c:21e3]
Ulisses Furquim (4):
Bluetooth: Remove global mutex hci_task_lock
Bluetooth: Always compile SCO and L2CAP in Bluetooth Core
Bluetooth: Make HCI call directly into SCO and L2CAP event functions
Bluetooth: Fix deadlocks with sock lock and L2CAP timers locks
drivers/bluetooth/btusb.c | 10 +-
include/net/bluetooth/bluetooth.h | 22 ----
include/net/bluetooth/hci.h | 14 ++-
include/net/bluetooth/hci_core.h | 162 +++++++++++---------------
include/net/bluetooth/l2cap.h | 40 ++++++-
include/net/bluetooth/smp.h | 6 +
net/bluetooth/Kconfig | 37 ++-----
net/bluetooth/Makefile | 5 +-
net/bluetooth/af_bluetooth.c | 11 +-
net/bluetooth/bnep/Kconfig | 2 +-
net/bluetooth/cmtp/Kconfig | 2 +-
net/bluetooth/hci_conn.c | 4 +-
net/bluetooth/hci_core.c | 172 +++++++++++-----------------
net/bluetooth/hci_event.c | 28 ++++-
net/bluetooth/hidp/Kconfig | 2 +-
net/bluetooth/l2cap_core.c | 112 ++++--------------
net/bluetooth/mgmt.c | 10 ++-
net/bluetooth/rfcomm/Kconfig | 2 +-
net/bluetooth/rfcomm/core.c | 44 +++-----
net/bluetooth/sco.c | 38 +------
net/bluetooth/smp.c | 235 +++++++++++++++++++++++++++++++++----
21 files changed, 499 insertions(+), 459 deletions(-)
next reply other threads:[~2011-12-27 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 16:21 Gustavo Padovan [this message]
2011-12-27 16:52 ` pull request: bluetooth-next 2011-12-27 Gustavo Padovan
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=20111227162103.GB8298@joana \
--to=padovan@profusion.mobi \
--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).