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 2020-06-01
Date: Mon, 1 Jun 2020 10:08:03 +0300 [thread overview]
Message-ID: <20200601070803.GA18009@jhedberg-mac01.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 2770 bytes --]
Hi Dave,
Here's one last bluetooth-next pull request for 5.8, which I hope can
still be accepted.
- Enabled Wide-Band Speech (WBS) support for Qualcomm wcn3991
- Multiple fixes/imprvovements to Qualcomm-based devices
- Fix GAP/SEC/SEM/BI-10-C qualfication test case
- Added support for Broadcom BCM4350C5 device
- Several other smaller fixes & improvements
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit dbfe7d74376e187f3c6eaff822e85176bc2cd06e:
rds: convert get_user_pages() --> pin_user_pages() (2020-05-17 12:37:45 -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 e5aeebddfc312ea7bb55dfe6c7264e71a3b43992:
Bluetooth: hci_qca: Fix QCA6390 memdump failure (2020-06-01 08:07:33 +0200)
----------------------------------------------------------------
Abhishek Pandit-Subedi (2):
Bluetooth: hci_qca: Enable WBS support for wcn3991
Bluetooth: hci_qca: Fix uninitialized access to hdev
Azamat H. Hackimov (1):
Bluetooth: btbcm: Added 003.006.007, changed 001.003.015
Chuhong Yuan (1):
Bluetooth: btmtkuart: Improve exception handling in btmtuart_probe()
Gustavo A. R. Silva (1):
Bluetooth: L2CAP: Replace zero-length array with flexible-array
Hsin-Yu Chao (1):
Bluetooth: Add SCO fallback for invalid LMP parameters error
Luiz Augusto von Dentz (2):
Bluetooth: Consolidate encryption handling in hci_encrypt_cfm
Bluetooth: Fix assuming EIR flags can result in SSP authentication
Sebastian Andrzej Siewior (1):
Bluetooth: Acquire sk_lock.slock without disabling interrupts
Zijun Hu (5):
Bluetooth: hci_qca: Fix suspend/resume functionality failure
Bluetooth: hci_qca: Fix qca6390 enable failure after warm reboot
Bluetooth: hci_qca: Improve controller ID info log level
Bluetooth: btmtkuart: Use serdev_device_write_buf() instead of serdev_device_write()
Bluetooth: hci_qca: Fix QCA6390 memdump failure
Łukasz Rymanowski (1):
Bluetooth: Fix for GAP/SEC/SEM/BI-10-C
drivers/bluetooth/btbcm.c | 3 +-
drivers/bluetooth/btmtkuart.c | 17 +++---
drivers/bluetooth/btqca.c | 14 +++--
drivers/bluetooth/hci_qca.c | 123 ++++++++++++++++++++++++++++++++-------
include/net/bluetooth/hci_core.h | 20 ++++++-
include/net/bluetooth/l2cap.h | 6 +-
net/bluetooth/hci_conn.c | 2 -
net/bluetooth/hci_event.c | 29 ++-------
net/bluetooth/rfcomm/sock.c | 7 +--
net/bluetooth/smp.c | 4 ++
10 files changed, 154 insertions(+), 71 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2020-06-01 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 7:08 Johan Hedberg [this message]
2020-06-01 18:01 ` pull request: bluetooth-next 2020-06-01 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=20200601070803.GA18009@jhedberg-mac01.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