Linux bluetooth development
 help / color / mirror / Atom feed
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-01-08
Date: Fri, 8 Jan 2016 12:46:22 +0200	[thread overview]
Message-ID: <20160108104622.GA20780@t440s.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 2355 bytes --]

Hi Dave,

Here's one more bluetooth-next pull request for the 4.5 kernel:

 - Support for CRC check and promiscuous mode for CC2520
 - Fixes to btmrvl driver
 - New ACPI IDs for hci_bcm driver
 - Limited Discovery support for the Bluetooth mgmt interface
 - Minor other cleanups here and there

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

Johan

---
The following changes since commit c07f30ad68053181b3e8a0e65b0630e12e844f91:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2015-12-31 18:20:10 -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 8cf60cf238ce1bea38593321e6ea8561fc32e38d:

  Bluetooth: btmrvl: don't send data to firmware while processing suspend (2016-01-06 16:37:14 +0100)

----------------------------------------------------------------
Brad Campbell (1):
      ieee802154: cc2520: Check CRC & add promiscuous

Chin-Ran Lo (3):
      Bluetooth: btmrvl: fix hung task warning dump
      Bluetooth: btmrvl: max out host sleep parameter 'gap'
      Bluetooth: btmrvl: don't send data to firmware while processing suspend

Heikki Krogerus (2):
      Bluetooth: hci_bcm: move all Broadcom ACPI IDs to BCM HCI driver
      Bluetooth: hci_bcm: new ACPI IDs

Johan Hedberg (2):
      Bluetooth: Change eir_has_data_type() to more generic eir_get_data()
      Bluetooth: Add support for Start Limited Discovery command

Johannes Berg (1):
      Bluetooth: avoid rebuilding hci_sock all the time

Julia Lawall (1):
      mac802154: constify ieee802154_llsec_ops structure

 drivers/bluetooth/btmrvl_drv.h   |   1 +
 drivers/bluetooth/btmrvl_main.c  |  13 +++-
 drivers/bluetooth/btmrvl_sdio.c  |   6 +-
 drivers/bluetooth/hci_bcm.c      |   7 ++
 drivers/net/ieee802154/cc2520.c  | 145 ++++++++++++++++++++++++++++++++------
 include/net/bluetooth/hci_core.h |  31 +++++---
 include/net/bluetooth/mgmt.h     |   2 +
 include/net/ieee802154_netdev.h  |   2 +-
 net/bluetooth/hci_event.c        |   6 +-
 net/bluetooth/hci_request.c      |  11 ++-
 net/bluetooth/hci_sock.c         |  27 ++++---
 net/bluetooth/mgmt.c             |  56 ++++++++++++---
 net/mac802154/mac_cmd.c          |   2 +-
 net/rfkill/rfkill-gpio.c         |   4 --
 14 files changed, 244 insertions(+), 69 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-01-08 10:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 10:46 Johan Hedberg [this message]
2016-01-08 18:17 ` pull request: bluetooth-next 2016-01-08 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=20160108104622.GA20780@t440s.lan \
    --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