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-08-18
Date: Fri, 18 Aug 2017 19:16:23 +0300 [thread overview]
Message-ID: <20170818161623.GA22628@x1c.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 2456 bytes --]
Hi Dave,
Here's one more bluetooth-next pull request for the 4.14 kernel:
- Multiple fixes for Broadcom controllers
- Fixes to the bluecard HCI driver
- New USB ID for Realtek RTL8723BE controller
- Fix static analyzer warning with kfree
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit 1afec92be0d7b516a79f4c548a81d17460c8ba73:
Merge branch 'sctp-remove-typedefs-from-structures-part-5' (2017-08-06 21:33:43 -0700)
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 01d5e44ace8a20fc51e0d530f98acb3c365345a5:
Bluetooth: hci_bcm: Handle empty packet after firmware loading (2017-08-17 22:51:50 +0300)
----------------------------------------------------------------
Colin Ian King (1):
Bluetooth: kfree tmp rather than an alias to it
Dmitry Tunin (1):
Bluetooth: Add support of 13d3:3494 RTL8723BE device
Loic Poulain (2):
Bluetooth: hci_bcm: Add serdev support
dt-bindings: net: bluetooth: Add broadcom-bluetooth
Marcel Holtmann (4):
Bluetooth: btusb: Add workaround for Broadcom devices without product id
Bluetooth: hci_bcm: Use operation speed of 4Mbps only for ACPI devices
Bluetooth: btbcm: Consolidate the controller information commands
Bluetooth: hci_bcm: Handle empty packet after firmware loading
Ondrej Zary (3):
Bluetooth: bluecard: Always enable LEDs (fix for Anycom CF-300)
Bluetooth: bluecard: fix LED behavior
Bluetooth: bluecard: blink LED during continuous activity
Pavel Machek (1):
Bluetooth: document config options
Sukumar Ghorai (1):
Bluetooth: btusb: driver to enable the usb-wakeup feature
.../devicetree/bindings/net/broadcom-bluetooth.txt | 35 +++++++
drivers/bluetooth/Kconfig | 1 +
drivers/bluetooth/bluecard_cs.c | 58 ++++++------
drivers/bluetooth/btbcm.c | 69 ++++++++------
drivers/bluetooth/btusb.c | 24 +++++
drivers/bluetooth/hci_bcm.c | 103 ++++++++++++++++++++-
net/bluetooth/Kconfig | 12 +++
net/bluetooth/selftest.c | 2 +-
8 files changed, 238 insertions(+), 66 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/broadcom-bluetooth.txt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2017-08-18 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 16:16 Johan Hedberg [this message]
2017-08-18 18:08 ` pull request: bluetooth-next 2017-08-18 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=20170818161623.GA22628@x1c.home \
--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