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-11-01
Date: Wed, 1 Nov 2017 10:32:13 +0200 [thread overview]
Message-ID: <20171101083213.GA20632@x1c.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 3020 bytes --]
Hi Dave,
Here's one more bluetooth-next pull request for the 4.15 kernel.
- New NFA344A device entry for btusb drvier
- Fix race conditions in hci_ldisc
- Fix for isochronous interface assignments in btusb driver
- A few other smaller fixes & improvements
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit fac72b243cc789bb209e6eca824919b42d98cfe2:
Bluetooth: mark expected switch fall-throughs (2017-10-14 09:25:51 +0200)
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 0338b1b393ec7910898e8f7b25b3bf31a7282e16:
Bluetooth: hci_ldisc: Fix another race when closing the tty. (2017-10-30 15:48:32 +0100)
----------------------------------------------------------------
Bartosz Chronowski (1):
Bluetooth: btusb: Add new NFA344A entry.
Jaganath Kanakkassery (1):
Bluetooth: Fix potential memory leak
Jaya P G (1):
Bluetooth: btusb: Update firmware filename for Intel 9x60 and later
Konrad Zapałowicz (1):
Bluetooth: increase timeout for le auto connections
Loic Poulain (1):
Bluetooth: hci_ath: Add ath_vendor_cmd helper
Marcel Holtmann (2):
Bluetooth: Use bt_dev_err and bt_dev_info when possible
Bluetooth: btusb: Fix isochronous interface assignments
Ronald Tschalär (2):
Bluetooth: hci_ldisc: Allow sleeping while proto locks are held.
Bluetooth: hci_ldisc: Fix another race when closing the tty.
Sebastian Andrzej Siewior (1):
Bluetooth: avoid recursive locking in hci_send_to_channel()
drivers/bluetooth/bpa10x.c | 15 ++-
drivers/bluetooth/bt3c_cs.c | 2 +-
drivers/bluetooth/btbcm.c | 103 +++++++++---------
drivers/bluetooth/btintel.c | 42 ++++----
drivers/bluetooth/btqca.c | 6 +-
drivers/bluetooth/btrtl.c | 21 ++--
drivers/bluetooth/btusb.c | 214 ++++++++++++++++++++++----------------
drivers/bluetooth/hci_ath.c | 51 +++++----
drivers/bluetooth/hci_h4.c | 2 +-
drivers/bluetooth/hci_ldisc.c | 42 ++++----
drivers/bluetooth/hci_qca.c | 12 +--
drivers/bluetooth/hci_serdev.c | 9 +-
drivers/bluetooth/hci_uart.h | 2 +-
include/net/bluetooth/bluetooth.h | 3 +
include/net/bluetooth/hci.h | 2 +-
net/bluetooth/a2mp.c | 2 +-
net/bluetooth/amp.c | 4 +-
net/bluetooth/hci_conn.c | 6 +-
net/bluetooth/hci_core.c | 35 +++----
net/bluetooth/hci_event.c | 46 ++++----
net/bluetooth/hci_request.c | 21 ++--
net/bluetooth/hci_request.h | 1 +
net/bluetooth/hci_sock.c | 17 +--
net/bluetooth/hci_sysfs.c | 2 +-
net/bluetooth/mgmt.c | 57 +++++-----
net/bluetooth/smp.c | 22 ++--
26 files changed, 407 insertions(+), 332 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2017-11-01 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 8:32 Johan Hedberg [this message]
2017-11-01 13:09 ` pull request: bluetooth-next 2017-11-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=20171101083213.GA20632@x1c.lan \
--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).