From: Johan Hedberg <johan.hedberg@gmail.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: pull request: bluetooth-next 2019-12-09
Date: Mon, 9 Dec 2019 14:48:07 +0200 [thread overview]
Message-ID: <20191209124807.GA7309@jhedberg-mac01.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]
Hi Dave,
Here's the first bluetooth-next pull request for 5.6:
- Devicetree bindings updates for Broadcom controllers
- Add support for PCM configuration for Broadcom controllers
- btusb: Fixes for Realtek devices
- butsb: A few other smaller fixes (mem leak & non-atomic allocation issue)
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit be2eca94d144e3ffed565c483a58ecc76a869c98:
Merge tag 'for-linus-5.5-1' of git://github.com/cminyard/linux-ipmi (2019-11-25 21:41:48 -0800)
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 7ecacafc240638148567742cca41aa7144b4fe1e:
Bluetooth: btusb: Disable runtime suspend on Realtek devices (2019-12-05 10:31:29 +0100)
----------------------------------------------------------------
Abhishek Pandit-Subedi (5):
Bluetooth: hci_bcm: Disallow set_baudrate for BCM4354
Bluetooth: btbcm: Support pcm configuration
dt-bindings: net: bluetooth: update broadcom-bluetooth
Bluetooth: hci_bcm: Support pcm params in dts
dt-bindings: net: bluetooth: Minor fix in broadcom-bluetooth
Colin Ian King (1):
Bluetooth: btusb: fix memory leak on fw
Johan Hovold (1):
Bluetooth: btusb: fix non-atomic allocation in completion handler
Kai-Heng Feng (1):
Bluetooth: btusb: Disable runtime suspend on Realtek devices
Max Chou (1):
Bluetooth: btusb: Edit the logical value for Realtek Bluetooth reset
.../devicetree/bindings/net/broadcom-bluetooth.txt | 7 +++
drivers/bluetooth/btbcm.c | 46 ++++++++++++++++++++
drivers/bluetooth/btbcm.h | 16 +++++++
drivers/bluetooth/btusb.c | 12 ++++--
drivers/bluetooth/hci_bcm.c | 50 +++++++++++++++++++++-
5 files changed, 125 insertions(+), 6 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-12-09 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 12:48 Johan Hedberg [this message]
2019-12-09 18:49 ` pull request: bluetooth-next 2019-12-09 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=20191209124807.GA7309@jhedberg-mac01.local \
--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).