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 2011-08-16
Date: Tue, 16 Aug 2011 13:59:05 -0300 [thread overview]
Message-ID: <20110816165905.GA27448@joana> (raw)
Hi John,
Some fixes for 3.1! It looks a lot of fixes but some of them are the same fix
applied to different files. Here we have a fix for a wrong timer value from
Chen Ganir, a lock balance fix from Dan Carpenter, regression fix with the HCI
Reset command from Szymon Janc, a fix to not show error messages on btusb
device disconnect from Paul Bolle. Support for Toshiba AR30XX from Ricardo
Mendoza. And finally a bunch of fixes from Peter Hurley, there are some lost
wake up, deadlocks and memort leaks fixes. Most of them fixes regressions
introduced by the move to the kthread API.
Please pull! Or let me know if disagree with something here. Thanks.
Gustavo
The following changes since commit 674db1344443204b6ce3293f2df8fd1b7665deea:
rt2x00: fix crash in rt2800usb_get_txwi (2011-08-11 14:34:37 -0400)
are available in the git repository at:
master.kernel.org:/pub/scm/linux/kernel/git/padovan/bluetooth.git master
Chen Ganir (1):
Bluetooth: Fixed wrong L2CAP Sock timer value
Dan Carpenter (1):
Bluetooth: unlock if allocation fails in hci_blacklist_add()
Paul Bolle (1):
Bluetooth: btusb: be quiet on device disconnect
Peter Hurley (15):
Bluetooth: rfcomm: Remove unnecessary krfcommd event
Bluetooth: rfcomm: Fix lost wakeups waiting to accept socket
Bluetooth: Fix lost wakeups waiting for sock state change
Bluetooth: l2cap: Fix lost wakeups waiting to accept socket
Bluetooth: sco: Fix lost wakeups waiting to accept socket
Bluetooth: bnep: Fix lost wakeup of session thread
Bluetooth: cmtp: Fix lost wakeup of session thread
Bluetooth: l2cap: Fix lost wakeup waiting for ERTM acks
Bluetooth: bnep: Fix deadlock in session deletion
Bluetooth: cmtp: Fix deadlock in session deletion
Bluetooth: hidp: Fix session cleanup on failed conn add
Bluetooth: hidp: Fix memory leak of cached report descriptor
Bluetooth: hidp: Only free input device if failed register
Bluetooth: hidp: Don't release device ref if never held
Bluetooth: cmtp: Fix session cleanup on failed conn add
Ricardo Mendoza (1):
Bluetooth: Add Toshiba laptops AR30XX device ID
Szymon Janc (1):
Bluetooth: Don't use cmd_timer to timeout HCI reset command
drivers/bluetooth/ath3k.c | 1 +
drivers/bluetooth/btusb.c | 13 ++++++++++---
net/bluetooth/af_bluetooth.c | 6 +++---
net/bluetooth/bnep/bnep.h | 1 +
net/bluetooth/bnep/core.c | 13 ++++++++-----
net/bluetooth/cmtp/capi.c | 3 ++-
net/bluetooth/cmtp/cmtp.h | 1 +
net/bluetooth/cmtp/core.c | 20 ++++++++++++--------
net/bluetooth/hci_core.c | 8 +++++---
net/bluetooth/hidp/core.c | 19 +++++++++----------
net/bluetooth/l2cap_core.c | 6 +++---
net/bluetooth/l2cap_sock.c | 30 +++++++++++++++---------------
net/bluetooth/rfcomm/core.c | 17 +++++++----------
net/bluetooth/rfcomm/sock.c | 28 ++++++++++++++--------------
net/bluetooth/sco.c | 28 ++++++++++++++--------------
15 files changed, 105 insertions(+), 89 deletions(-)
reply other threads:[~2011-08-16 16:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110816165905.GA27448@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