2014-12-12 17:44:44

by Johan Hedberg

[permalink] [raw]
Subject: pull request: bluetooth 2014-12-12

Hi John,

These fixes are intended for 3.19, note that the tree to pull from is
bluetooth-next (unlike the subject implies). I'd have normally done a
pull request from bluetooth.git, but since these fixes for 3.19 is all
we have so far I thought it's simpler if you just pull from our -next
tree. The patches consist of:

- Coccinelle warning fix
- hci_dev_lock/unlock fixes
- Fixes for pending mgmt command handling
- Fixes for properly following the force_lesc_support switch
- Fix for a Microsoft branded Broadcom adapter
- New device id for Atheros AR3012
- Fix for BR/EDR Secure Connections enabling

Please let me know if there are any issues pulling. Thanks.

Johan

---
The following changes since commit 5a34bd5f5d8119def4feb1d2b4e3906b71059416:

Bluetooth: Enable events for P-256 Public Key and DHKey commands (2014-12-05 18:17:49 +0200)

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 9845904fd489288bcf693642c1b31cc463c0b660:

Bluetooth: Fix mgmt response status when removing adapter (2014-12-12 13:20:12 +0100)

----------------------------------------------------------------
Fengguang Wu (1):
Bluetooth: fix err_cast.cocci warnings

Jaganath Kanakkassery (2):
Bluetooth: Fix missing hci_dev_lock/unlock in mgmt req_complete()
Bluetooth: Fix missing hci_dev_lock/unlock in hci_event

Janne Heikkinen (1):
Bluetooth: Add USB device 04ca:3010 as Atheros AR3012

Johan Hedberg (5):
Bluetooth: Fix calling hci_conn_put too early
Bluetooth: Fix incorrect pending cmd removal in pairing_complete()
Bluetooth: Fix notifying mgmt power off before flushing connection list
Bluetooth: Fix enabling BR/EDR SC when powering on
Bluetooth: Fix mgmt response status when removing adapter

Marcel Holtmann (4):
Bluetooth: Check for force_lesc_support when enabling SMP over BR/EDR
Bluetooth: Check for force_lesc_support before rejecting SMP over BR/EDR
Bluetooth: Fix generation of non-resolvable private addresses
Bluetooth: Fix check for support for page scan related commands

drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
net/bluetooth/hci_conn.c | 2 +-
net/bluetooth/hci_core.c | 60 +++++++++++++++++++-------------
net/bluetooth/hci_event.c | 20 +++++++++++
net/bluetooth/l2cap_core.c | 5 +--
net/bluetooth/mgmt.c | 85 ++++++++++++++++++++++++++++++++-------------
net/bluetooth/smp.c | 5 +--
8 files changed, 126 insertions(+), 54 deletions(-)


Attachments:
(No filename) (2.55 kB)
(No filename) (819.00 B)
Download all attachments

2014-12-15 18:30:12

by John W. Linville

[permalink] [raw]
Subject: Re: pull request: bluetooth 2014-12-12

On Fri, Dec 12, 2014 at 07:44:35PM +0200, Johan Hedberg wrote:
> Hi John,
>
> These fixes are intended for 3.19, note that the tree to pull from is
> bluetooth-next (unlike the subject implies). I'd have normally done a
> pull request from bluetooth.git, but since these fixes for 3.19 is all
> we have so far I thought it's simpler if you just pull from our -next
> tree. The patches consist of:
>
> - Coccinelle warning fix
> - hci_dev_lock/unlock fixes
> - Fixes for pending mgmt command handling
> - Fixes for properly following the force_lesc_support switch
> - Fix for a Microsoft branded Broadcom adapter
> - New device id for Atheros AR3012
> - Fix for BR/EDR Secure Connections enabling
>
> Please let me know if there are any issues pulling. Thanks.
>
> Johan
>
> ---
> The following changes since commit 5a34bd5f5d8119def4feb1d2b4e3906b71059416:
>
> Bluetooth: Enable events for P-256 Public Key and DHKey commands (2014-12-05 18:17:49 +0200)
>
> 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 9845904fd489288bcf693642c1b31cc463c0b660:
>
> Bluetooth: Fix mgmt response status when removing adapter (2014-12-12 13:20:12 +0100)

Pulling now...

--
John W. Linville Someday the world will need a hero, and you
[email protected] might be all we have. Be ready.