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 2018-10-20
Date: Sat, 20 Oct 2018 12:03:42 +0300 [thread overview]
Message-ID: <20181020090342.GA14926@x1c.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]
Hi Dave,
Here's one more bluetooth-next pull request for the 4.20 kernel.
- Added new USB ID for QCA_ROME controller
- Added debug trace support from QCA wcn3990 controllers
- Updated L2CAP to conform to latest Errata Service Release
- Fix binding to non-removable BCM43430 devices
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit d864991b220b7c62e81d21209e1fd978fd67352c:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2018-10-12 21:38:46 -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 c614ca3f7476934de54dd731e09d094ad822696c:
Bluetooth: hci_qca: Add support for controller debug logs. (2018-10-18 09:55:16 +0200)
----------------------------------------------------------------
Balakrishna Godavarthi (1):
Bluetooth: hci_qca: Add support for controller debug logs.
Cho, Yu-Chen (1):
Bluetooth: btsdio: Do not bind to non-removable BCM43430
Colin Ian King (1):
Bluetooth: Remove redundant check on status
Mallikarjun Phulari (2):
Bluetooth: Use separate L2CAP LE credit based connection result values
Bluetooth: Errata Service Release 8, Erratum 3253
Owen Lin (1):
Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device
drivers/bluetooth/btsdio.c | 14 +++++++++-----
drivers/bluetooth/btusb.c | 1 +
drivers/bluetooth/hci_qca.c | 19 ++++++++++++++++++-
include/net/bluetooth/l2cap.h | 19 +++++++++++++------
net/bluetooth/hci_event.c | 38 +++++++++++++++++---------------------
net/bluetooth/l2cap_core.c | 36 ++++++++++++++++++++++--------------
6 files changed, 80 insertions(+), 47 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2018-10-20 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 9:03 Johan Hedberg [this message]
2018-10-20 19:34 ` pull request: bluetooth-next 2018-10-20 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=20181020090342.GA14926@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;
as well as URLs for NNTP newsgroup(s).