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-09-03
Date: Sun, 3 Sep 2017 09:20:55 +0300 [thread overview]
Message-ID: <20170903062055.GA9569@x1c.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
Hi Dave,
Here's one last bluetooth-next pull request for the 4.14 kernel:
- NULL pointer fix in ca8210 802.15.4 driver
- A few "const" fixes
- New Kconfig option for disabling legacy interfaces
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit 01d300c577c72229b0a3b09e194cae52b219d5b3:
Merge branch 'amd-xgbe-next' (2017-08-18 16:30:17 -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 65bce46298d064dff9db1282e17bb26602715819:
Bluetooth: make baswap src const (2017-09-01 22:49:47 +0200)
----------------------------------------------------------------
Bhumika Goyal (2):
Bluetooth: make device_type const
ieee802154: 6lowpan: make header_ops const
Christophe JAILLET (1):
ieee802154: ca8210: Fix a potential NULL pointer dereference
Loic Poulain (1):
Bluetooth: make baswap src const
Marcel Holtmann (1):
Bluetooth: Add option for disabling legacy ioctl interfaces
drivers/net/ieee802154/ca8210.c | 5 +----
include/net/bluetooth/bluetooth.h | 2 +-
net/bluetooth/Kconfig | 10 ++++++++++
net/bluetooth/hci_sock.c | 6 ++++++
net/bluetooth/hci_sysfs.c | 4 ++--
net/bluetooth/lib.c | 6 +++---
net/ieee802154/6lowpan/core.c | 2 +-
7 files changed, 24 insertions(+), 11 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2017-09-03 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 6:20 Johan Hedberg [this message]
2017-09-04 4:28 ` pull request: bluetooth-next 2017-09-03 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=20170903062055.GA9569@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).