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-11-24
Date: Sun, 24 Nov 2019 15:26:45 +0200 [thread overview]
Message-ID: <20191124132645.GA43125@pehoward-mobl1.ger.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]
Hi Dave,
Here's one last bluetooth-next pull request for the 5.5 kernel:
- Fix BDADDR_PROPERTY & INVALID_BDADDR quirk handling
- Added support for BCM4334B0 and BCM4335A0 controllers
- A few other smaller fixes related to locking and memory leaks
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit 90bc72b13c08eedf73b7c0bd94ef23c467800c4a:
Merge branch 'ARM-Enable-GENET-support-for-RPi-4' (2019-11-12 20:08:00 -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 a4f95f31a9f38d9bb1fd313fcc2d0c0d48116ee3:
Bluetooth: btbcm: Use the BDADDR_PROPERTY quirk (2019-11-22 13:35:20 +0100)
----------------------------------------------------------------
Andre Heider (1):
Bluetooth: btbcm: Use the BDADDR_PROPERTY quirk
Dan Carpenter (1):
Bluetooth: delete a stray unlock
Marcel Holtmann (1):
Bluetooth: Allow combination of BDADDR_PROPERTY and INVALID_BDADDR quirks
Mohammad Rasim (2):
dt-bindings: net: Add compatible for BCM4335A0 bluetooth
Bluetooth: btbcm: Add entry for BCM4335A0 UART bluetooth
Navid Emamdoost (1):
Bluetooth: Fix memory leak in hci_connect_le_scan
Oliver Neukum (1):
Bluetooth: btusb: fix PM leak in error case of setup
Stephan Gerhold (1):
Bluetooth: btbcm: Add entry for BCM4334B0 UART Bluetooth
.../devicetree/bindings/net/broadcom-bluetooth.txt | 1 +
drivers/bluetooth/btbcm.c | 10 +++++++++
drivers/bluetooth/btusb.c | 3 ++-
drivers/bluetooth/hci_bcm.c | 1 +
net/bluetooth/hci_conn.c | 4 +++-
net/bluetooth/hci_core.c | 26 ++++++++++++++++++++--
net/bluetooth/l2cap_core.c | 4 +---
7 files changed, 42 insertions(+), 7 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-11-24 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-24 13:26 Johan Hedberg [this message]
2019-11-25 2:58 ` pull request: bluetooth-next 2019-11-24 Jakub Kicinski
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=20191124132645.GA43125@pehoward-mobl1.ger.corp.intel.com \
--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