From: Johan Hedberg <johan.hedberg@gmail.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: pull request: bluetooth-next 2014-07-31
Date: Thu, 31 Jul 2014 10:43:57 +0300 [thread overview]
Message-ID: <20140731074357.GA26071@t440s.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 2860 bytes --]
Hi John,
Here's one more (hopefully last) pull request for 3.17.
We've got:
- 6lowpan fixes/cleanups
- A couple crash fixes, one for the Marvell HCI driver and another in LE SMP.
- Fix for an incorrect connected state check
- Fix for the bondable requirement during pairing (an issue which had
crept in because of using "pairable" when in fact the actual meaning
was "bondable" (these have different meanings in Bluetooth)
Let me know if there are any issues. Thanks.
Johan
---
The following changes since commit 568ba389be505f505b7fbeedb9ab4ece27603fc9:
brcmfmac: Fix OOB interrupt not working for BCM43362 (2014-07-29 10:32:57 -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 8500d791c458ccbbb3e2d3fa9a0320ffd5729069:
Bluetooth: Fix crash in the Marvell driver initialization codepath (2014-07-31 01:07:28 +0200)
----------------------------------------------------------------
Alexander Aring (7):
6lowpan: iphc: rename hc06_ptr pointer to hc_ptr
6lowpan: iphc: use sizeof in udp uncompression
6lowpan: iphc: cleanup use of lowpan_fetch_skb
6lowpan: iphc: cleanup use of lowpan_push_hc_data
6lowpan: iphc: use ipv6 api to check address scope
6lowpan: iphc: remove check on null
6lowpan: remove unused LOWPAN_FRAG_SIZE define
Anatol Pomozov (1):
Bluetooth: Fix crash in the Marvell driver initialization codepath
Johan Hedberg (5):
Bluetooth: Fix SMP context tracking leading to a kernel crash
Bluetooth: Fix check for connected state when pairing
Bluetooth: Rename HCI_PAIRABLE to HCI_BONDABLE
Bluetooth: Rename pairable mgmt setting to bondable
Bluetooth: Always use non-bonding requirement when not bondable
Marcel Holtmann (6):
6lowpan: iphc: Fix block comments to match networking style
6lowpan: iphc: Fix issues with alignment matching open parenthesis
6lowpan: iphc: Fix missing blank line after variable declarations
6lowpan: iphc: Fix missing braces for if statement
6lowpan: iphc: Fix parenthesis alignments which off-by-one
Bluetooth: Fix sparse warning from HID new leds handling
Varka Bhadram (2):
6lowpan: remove unused macros
6lowpan: remove unused function
drivers/bluetooth/btmrvl_main.c | 5 +
include/net/6lowpan.h | 50 ------
include/net/bluetooth/hci.h | 2 +-
include/net/bluetooth/mgmt.h | 4 +-
net/6lowpan/iphc.c | 295 +++++++++++++++++-------------------
net/bluetooth/hci_core.c | 4 +-
net/bluetooth/hci_event.c | 15 +-
net/bluetooth/hidp/core.c | 2 +-
net/bluetooth/mgmt.c | 24 +--
net/bluetooth/smp.c | 17 ++-
10 files changed, 185 insertions(+), 233 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-07-31 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 7:43 Johan Hedberg [this message]
2014-07-31 17:38 ` pull request: bluetooth-next 2014-07-31 John W. Linville
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=20140731074357.GA26071@t440s.lan \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).