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 2016-04-12
Date: Tue, 12 Apr 2016 11:08:15 +0300 [thread overview]
Message-ID: <20160412080815.GA17516@t440s> (raw)
[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]
Hi Dave,
Here's a set of Bluetooth & 802.15.4 patches intended for the 4.7 kernel:
- Fix for race condition in vhci driver
- Memory leak fix for ieee802154/adf7242 driver
- Improvements to deal with single-mode (LE-only) Bluetooth controllers
- Fix for allowing the BT_SECURITY_FIPS security level
- New BCM2E71 ACPI ID
- NULL pointer dereference fix fox hci_ldisc driver
Let me know if there are any issues pulling. Thanks.
Johan
----
The following changes since commit 9ef280c6c28f0c01aa9d909263ad47c796713a8e:
irda: sh_irda: remove driver (2016-04-04 16:24:13 -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 8805eea2494a2837983bc4aaaf6842c89666ec25:
Bluetooth: hci_bcsp: fix code style (2016-04-08 23:01:36 +0200)
----------------------------------------------------------------
Alexander Aring (1):
6lowpan: iphc: fix handling of link-local compression
Jiri Slaby (2):
Bluetooth: vhci: fix open_timeout vs. hdev race
Bluetooth: vhci: purge unhandled skbs
Johan Hedberg (2):
Bluetooth: Fix setting NO_BREDR advertising flag
Bluetooth: Ignore unknown advertising packet types
Loic Poulain (2):
Bluetooth: hci_bcm: Add BCM2E71 ACPI ID
Bluetooth: hci_ldisc: Fix null pointer derefence in case of early data
Maxim Zhukov (1):
Bluetooth: hci_bcsp: fix code style
Patrik Flykt (1):
Bluetooth: Allow setting BT_SECURITY_FIPS with setsockopt
Sudip Mukherjee (1):
ieee802154/adf7242: fix memory leak of firmware
drivers/bluetooth/hci_bcm.c | 1 +
drivers/bluetooth/hci_bcsp.c | 57 +++++++++++++++++++++++++++++++--------------------------
drivers/bluetooth/hci_ldisc.c | 11 +++++++----
drivers/bluetooth/hci_uart.h | 1 +
drivers/bluetooth/hci_vhci.c | 9 ++++++---
drivers/net/ieee802154/adf7242.c | 2 ++
net/6lowpan/iphc.c | 11 +++++++++--
net/bluetooth/hci_event.c | 13 +++++++++++++
net/bluetooth/hci_request.c | 6 +++---
net/bluetooth/l2cap_sock.c | 2 +-
10 files changed, 74 insertions(+), 39 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-04-12 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 8:08 Johan Hedberg [this message]
2016-04-12 15:58 ` pull request: bluetooth-next 2016-04-12 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=20160412080815.GA17516@t440s \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.