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 2018-01-11
Date: Thu, 11 Jan 2018 10:24:34 +0200 [thread overview]
Message-ID: <20180111082434.GA12753@x1c.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 2683 bytes --]
Hi Dave,
Here's likely the last bluetooth-next pull request for the 4.16 kernel.
- Added support for Bluetooth on 2015+ MacBook (Pro)
- Fix to QCA Rome suspend/resume handling
- Two new QCA_ROME USB IDs in btusb
- A few other minor fixes
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit 18feb87105c3c16dc01e6981a6aafb175679b997:
enic: add wq clean up budget (2017-12-26 13:10:07 -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 ff8759609d021c0e85945fcc4a148a0e55ace70f:
Bluetooth: btbcm: Fix sleep mode struct ordering (2018-01-10 19:00:14 +0100)
----------------------------------------------------------------
AceLan Kao (1):
Bluetooth: btusb: Add support for 0cf3:e010
Arnd Bergmann (1):
Bluetooth: hciuart: add nvmem dependency
Colin Ian King (2):
Bluetooth: bpa10x: make array 'req' static, shrinks object size
Bluetooth: btintel: make array 'param' static, shrinks object size
Hans de Goede (1):
Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a "rewritten" version
Ioan Moldovan (1):
Bluetooth: Add a new 04ca:3015 QCA_ROME device
Kai-Heng Feng (1):
Revert "Bluetooth: btusb: fix QCA Rome suspend/resume"
Lukas Wunner (15):
Bluetooth: Avoid WARN splat due to missing GPIOLIB
Bluetooth: hci_bcm: Streamline runtime PM code
Bluetooth: Depend on rather than select GPIOLIB
Bluetooth: hci_bcm: Mandate presence of shutdown and device wake GPIO
Bluetooth: hci_bcm: Clean up unnecessary #ifdef
Bluetooth: hci_bcm: Fix race on close
Bluetooth: hci_bcm: Fix unbalanced pm_runtime_disable()
Bluetooth: hci_bcm: Invalidate IRQ on request failure
Bluetooth: hci_bcm: Document struct bcm_device
Bluetooth: hci_bcm: Add callbacks to toggle GPIOs
Bluetooth: hci_bcm: Handle errors properly
Bluetooth: hci_bcm: Support Apple GPIO handling
Bluetooth: hci_bcm: Silence IRQ printk
Bluetooth: hci_bcm: Sleep instead of spinning
Bluetooth: btbcm: Fix sleep mode struct ordering
Ronald Tschalär (1):
Bluetooth: hci_bcm: Validate IRQ before using it
drivers/bluetooth/Kconfig | 4 +
drivers/bluetooth/bpa10x.c | 2 +-
drivers/bluetooth/btbcm.h | 2 +-
drivers/bluetooth/btintel.c | 2 +-
drivers/bluetooth/btusb.c | 22 ++--
drivers/bluetooth/hci_bcm.c | 239 +++++++++++++++++++++++++++++++++++---------
6 files changed, 207 insertions(+), 64 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2018-01-11 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 8:24 Johan Hedberg [this message]
[not found] ` <20180111082434.GA12753-IWfI2fE34AE@public.gmane.org>
2018-01-11 18:58 ` pull request: bluetooth-next 2018-01-11 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=20180111082434.GA12753@x1c.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;
as well as URLs for NNTP newsgroup(s).