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-07-01
Date: Sat, 1 Jul 2017 21:19:50 +0300 [thread overview]
Message-ID: <20170701181950.GA27217@x1c.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 2179 bytes --]
Hi Dave,
Here are some more Bluetooth patches for the 4.13 kernel:
- Added support for Broadcom BCM43430 controllers
- Added sockaddr length checks before accessing sa_family
- Fixed possible "might sleep" errors in bnep, cmtp and hidp modules
- A few other minor fixes
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit 4b943faedfc29eda882851b772c06cecdf78d8e3:
udp/v6: prefetch rmem_alloc in udp6_queue_rcv_skb() (2017-06-22 13:44:04 -0400)
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 feb16722b5d5f05b7ae1278a43e717c3d35cd512:
Bluetooth: btbcm: Add entry for BCM43430 UART bluetooth (2017-06-29 14:39:42 +0200)
----------------------------------------------------------------
Colin Ian King (1):
Bluetooth: hci_serdev: make hci_serdev_client_ops static
Hans de Goede (1):
Bluetooth: hci_bcm: Add active_low irq polarity quirk for Asus T100CHI
Ian Molton (1):
Bluetooth: btbcm: Add entry for BCM43430 UART bluetooth
Jeffy Chen (3):
Bluetooth: bnep: fix possible might sleep error in bnep_session
Bluetooth: cmtp: fix possible might sleep error in cmtp_session
Bluetooth: hidp: fix possible might sleep error in hidp_session_thread
Loic Poulain (1):
Bluetooth: hci_bcm: Fix unwanted error reporting if no bcm dev
Mateusz Jurczyk (1):
Bluetooth: Add sockaddr length checks before accessing sa_family in bind and connect handlers
Tejun Heo (1):
bluetooth: remove WQ_MEM_RECLAIM from hci workqueues
drivers/bluetooth/btbcm.c | 1 +
drivers/bluetooth/hci_bcm.c | 12 ++++++++++--
drivers/bluetooth/hci_serdev.c | 4 ++--
net/bluetooth/bnep/core.c | 11 +++++------
net/bluetooth/cmtp/core.c | 17 ++++++++++-------
net/bluetooth/hci_core.c | 7 +++----
net/bluetooth/hidp/core.c | 33 ++++++++++++++++++++++-----------
net/bluetooth/l2cap_sock.c | 5 +++--
net/bluetooth/rfcomm/sock.c | 3 ++-
net/bluetooth/sco.c | 6 ++----
10 files changed, 60 insertions(+), 39 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2017-07-01 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 18:19 Johan Hedberg [this message]
2017-07-01 22:58 ` pull request: bluetooth-next 2017-07-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=20170701181950.GA27217@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).