From: Gustavo Padovan <gustavo@padovan.org>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: pull request: bluetooth 2012-08-06
Date: Mon, 6 Aug 2012 16:04:16 -0300 [thread overview]
Message-ID: <20120806190416.GE3146@joana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]
Hi John,
Here goes some fixes for 3.6-rc1, there are a few fix to thte inquiry code by
Ram Malovany, support for 2 new devices, and few others fixes for NULL
dereference, possible deadlock and a memory leak.
Please pull, or let me know of any problems with this! Thanks.
Gustavo
---
The following changes since commit d4e5979c0da95791aa717c18e162540c7a596360:
ath9k: Add PID/VID support for AR1111 (2012-08-03 10:11:14 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth master
for you to fetch changes up to 2096ae6ca647302d50a68aa36cb66a00e7dfac70:
Bluetooth: add support for atheros 0489:e057 (2012-08-06 15:33:05 -0300)
----------------------------------------------------------------
Andrei Emeltchenko (1):
Bluetooth: smp: Fix possible NULL dereference
Gustavo Padovan (1):
Bluetooth: Fix possible deadlock in SCO code
Jaganath Kanakkassery (1):
Bluetooth: Fix socket not getting freed if l2cap channel create fails
Manoj Iyer (1):
Bluetooth: btusb: Add vendor specific ID (0a5c:21f4) BCM20702A0
Peng Chen (1):
Bluetooth: add support for atheros 0489:e057
Ram Malovany (3):
Bluetooth: Fix using NULL inquiry entry
Bluetooth: Fix using a NULL inquiry cache entry
Bluetooth: Set name_state to unknown when entry name is empty
Szymon Janc (1):
Bluetooth: Fix legacy pairing with some devices
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 2 ++
net/bluetooth/hci_event.c | 28 ++++++++++++++++++++++------
net/bluetooth/l2cap_core.c | 1 +
net/bluetooth/l2cap_sock.c | 2 +-
net/bluetooth/sco.c | 19 +++++++++----------
net/bluetooth/smp.c | 5 ++++-
7 files changed, 41 insertions(+), 18 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2012-08-06 19:04 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=20120806190416.GE3146@joana \
--to=gustavo@padovan.org \
--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).