From: Johan Hedberg <johan.hedberg@gmail.com>
To: davem@davemloft.net
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: pull request: bluetooth-next 2017-02-19
Date: Sun, 19 Feb 2017 07:39:56 -0800 [thread overview]
Message-ID: <20170219153956.GA28473@x1c> (raw)
[-- Attachment #1: Type: text/plain, Size: 3133 bytes --]
Hi Dave,
Here's a set of Bluetooth patches for the 4.11 kernel:
- New USB IDs to the btusb driver
- Race fix in btmrvl driver
- Added out-of-band wakeup support to the btusb driver
- NULL dereference fix to bt_sock_recvmsg
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit b973154a2278c6af0b0efefafb222e0189959659:
atm: idt77252, use setup_timer and mod_timer (2017-02-15 13:24:53 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git for-upstream
for you to fetch changes up to 8f91566f99fab8f7a0d2728a1e3defb13675837a:
btmrvl: fix spelling mistake: "actived" -> "activated" (2017-02-19 00:26:37 +0100)
----------------------------------------------------------------
Christoph Haag (1):
Bluetooth: btusb: add support for 0bb4:0306
Colin Ian King (4):
Bluetooth: btmrvl: fix spelling mistake: "caibration" -> "calibration"
Bluetooth: fix spelling mistake: "advetising" -> "advertising"
Bluetooth: hci_qca: fix spelling mistake: "Spurrious" -> "Spurious"
btmrvl: fix spelling mistake: "actived" -> "activated"
Daniel Drake (1):
Bluetooth: hci_bcm: Add support for BCM2E95 and BCM2E96
Dmitry Tunin (1):
Bluetooth: Add another AR3012 04ca:3018 device
Ezequiel Garcia (1):
Bluetooth: Fix NULL pointer dereference in bt_sock_recvmsg
Javier Martinez Canillas (2):
Bluetooth: btqcomsmd: Fix module autoload
Bluetooth: btqcomsmd: Allow driver to build if COMPILE_TEST is enabled
Jeffy Chen (3):
btmrvl: avoid double-disable_irq() race
btmrvl: set irq_bt to -1 when failed to parse it
btmrvl: use dt's irqflags for wakeup pin
Rajat Jain (3):
Bluetooth: btusb: Use an error label for error paths
Bluetooth: btusb: Add out-of-band wakeup support
Bluetooth: btusb: Configure Marvell to use one of the pins for oob wakeup
Wen-chien Jesse Sung (2):
Bluetooth: btusb: Add support for 413c:8143
Bluetooth: btbcm: Add a delay for module reset
Documentation/devicetree/bindings/net/btusb.txt | 43 ++++++
.../{marvell-bt-sd8xxx.txt => marvell-bt-8xxx.txt} | 46 +++++-
drivers/bluetooth/Kconfig | 2 +-
drivers/bluetooth/ath3k.c | 2 +
drivers/bluetooth/btbcm.c | 3 +
drivers/bluetooth/btmrvl_main.c | 2 +-
drivers/bluetooth/btmrvl_sdio.c | 14 +-
drivers/bluetooth/btqcomsmd.c | 1 +
drivers/bluetooth/btusb.c | 164 +++++++++++++++++++--
drivers/bluetooth/hci_bcm.c | 68 ++++++---
drivers/bluetooth/hci_qca.c | 4 +-
net/bluetooth/af_bluetooth.c | 2 +-
net/bluetooth/hci_event.c | 2 +-
13 files changed, 300 insertions(+), 53 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/btusb.txt
rename Documentation/devicetree/bindings/net/{marvell-bt-sd8xxx.txt => marvell-bt-8xxx.txt} (50%)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2017-02-19 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 15:39 Johan Hedberg [this message]
2017-02-20 16:15 ` pull request: bluetooth-next 2017-02-19 David Miller
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=20170219153956.GA28473@x1c \
--to=johan.hedberg@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=netdev@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).