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 2016-12-03
Date: Sat, 3 Dec 2016 19:53:41 +0000 [thread overview]
Message-ID: <20161203195341.GA17607@x1c.ukservers.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2179 bytes --]
Hi Dave,
Here's a set of Bluetooth & 802.15.4 patches for net-next (i.e. 4.10
kernel):
- Fix for a potential NULL deref in the ieee802154 netlink code
- Fix for the ED values of the at86rf2xx driver
- Documentation updates to ieee802154
- Cleanups to u8 vs __u8 usage
- Timer API usage cleanups in HCI drivers
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit 0b42f25d2f123bb7fbd3565d003a8ea9e1e810fe:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2016-11-26 23:42:21 -0500)
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 6bf0d84d13e968b4f8bf0710e0cae785e228dbba:
docs: ieee802154: update main documentation file (2016-11-30 12:33:07 +0100)
----------------------------------------------------------------
Alexander Aring (1):
at86rf230: fix cca ed values for rf233
Pavel Machek (1):
Bluetooth: __ variants of u8 and friends are not neccessary inside kernel
Prasanna Karthik (3):
Bluetooth: hci_bcsp: Use setup_timer Kernel API instead of init_timer
Bluetooth: hci_h5: Use setup_timer Kernel API instead of init_timer
Bluetooth: hci_qca: Use setup_timer Kernel API instead of init_timer
Stefan Schmidt (3):
ieee802154: add myself as co-maintainer to MAINTAINERS file
ieee802154: fakelb: print number of created fake devices during probe
docs: ieee802154: update main documentation file
vegard.nossum@oracle.com (1):
ieee802154: check device type
Documentation/networking/ieee802154.txt | 26 +++++++++++---------------
MAINTAINERS | 1 +
drivers/bluetooth/hci_bcsp.c | 4 +---
drivers/bluetooth/hci_h5.c | 4 +---
drivers/bluetooth/hci_qca.c | 9 +++------
drivers/net/ieee802154/at86rf230.c | 16 +++++++++++-----
drivers/net/ieee802154/fakelb.c | 2 +-
include/net/bluetooth/bluetooth.h | 25 +++++++++++++------------
net/ieee802154/nl-phy.c | 6 +++++-
9 files changed, 47 insertions(+), 46 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2016-12-03 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 19:53 Johan Hedberg [this message]
2016-12-05 18:38 ` pull request: bluetooth-next 2016-12-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=20161203195341.GA17607@x1c.ukservers.net \
--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).