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-02-15
Date: Thu, 15 Feb 2018 10:33:59 +0200 [thread overview]
Message-ID: <20180215083359.GA593@x1c.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 2248 bytes --]
Hi Dave,
Here's the first bluetooth-next pull request targetting the 4.17 kernel
release.
- Fixes & cleanups to Atheros and Marvell drivers
- Support for two new Realtek controllers
- Support for new Intel Bluetooth controller
- Fix for supporting multiple slave-role Bluetooth LE connections
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit 617aebe6a97efa539cc4b8a52adccd89596e6be0:
Merge tag 'usercopy-v4.16-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux (2018-02-03 16:25:42 -0800)
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 907f84990924bf3a8d248c040dabeb5127ae6938:
Bluetooth: btrtl: Add RTL8723D and RTL8821C devices (2018-02-11 21:50:35 +0100)
----------------------------------------------------------------
Alex Lu (1):
Bluetooth: btrtl: Add RTL8723D and RTL8821C devices
Jia-Ju Bai (3):
Bluetooth: hci_ath: Replace mdelay with msleep in ath_wakeup_ar3k
Bluetooth: btmrvl_main: Replace GFP_ATOMIC with GFP_KERNEL in btmrvl_send_sync_cmd
Bluetooth: hci_ll: Replace mdelay with msleep in download_firmware
Larry Finger (1):
Bluetooth: btusb: Add device ID for RTL8822BE
Maxim Zhukov (5):
Bluetooth: ath3k: replace hardcode numbers with define
Bluetooth: ath3k: do not init variables
Bluetooth: ath3k: remove blank line after if
Bluetooth: ath3k: Fix warning: quoted string split across lines
Bluetooth: ath3k: fix checkpatch warning
Tedd Ho-Jeong An (1):
Bluetooth: btusb: Add support for Intel Bluetooth device 22560 [8087:0026]
Łukasz Rymanowski (1):
Bluetooth: Fix incorrect bits for LE states
drivers/bluetooth/ath3k.c | 28 ++++++----
drivers/bluetooth/btmrvl_main.c | 2 +-
drivers/bluetooth/btrtl.c | 119 ++++++++++++++++++++++++++++------------
drivers/bluetooth/btusb.c | 10 ++++
drivers/bluetooth/hci_ath.c | 4 +-
drivers/bluetooth/hci_ll.c | 2 +-
net/bluetooth/hci_request.c | 6 +-
7 files changed, 118 insertions(+), 53 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hedberg <johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org
Cc: linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: pull request: bluetooth-next 2018-02-15
Date: Thu, 15 Feb 2018 10:33:59 +0200 [thread overview]
Message-ID: <20180215083359.GA593@x1c.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 2248 bytes --]
Hi Dave,
Here's the first bluetooth-next pull request targetting the 4.17 kernel
release.
- Fixes & cleanups to Atheros and Marvell drivers
- Support for two new Realtek controllers
- Support for new Intel Bluetooth controller
- Fix for supporting multiple slave-role Bluetooth LE connections
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit 617aebe6a97efa539cc4b8a52adccd89596e6be0:
Merge tag 'usercopy-v4.16-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux (2018-02-03 16:25:42 -0800)
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 907f84990924bf3a8d248c040dabeb5127ae6938:
Bluetooth: btrtl: Add RTL8723D and RTL8821C devices (2018-02-11 21:50:35 +0100)
----------------------------------------------------------------
Alex Lu (1):
Bluetooth: btrtl: Add RTL8723D and RTL8821C devices
Jia-Ju Bai (3):
Bluetooth: hci_ath: Replace mdelay with msleep in ath_wakeup_ar3k
Bluetooth: btmrvl_main: Replace GFP_ATOMIC with GFP_KERNEL in btmrvl_send_sync_cmd
Bluetooth: hci_ll: Replace mdelay with msleep in download_firmware
Larry Finger (1):
Bluetooth: btusb: Add device ID for RTL8822BE
Maxim Zhukov (5):
Bluetooth: ath3k: replace hardcode numbers with define
Bluetooth: ath3k: do not init variables
Bluetooth: ath3k: remove blank line after if
Bluetooth: ath3k: Fix warning: quoted string split across lines
Bluetooth: ath3k: fix checkpatch warning
Tedd Ho-Jeong An (1):
Bluetooth: btusb: Add support for Intel Bluetooth device 22560 [8087:0026]
Łukasz Rymanowski (1):
Bluetooth: Fix incorrect bits for LE states
drivers/bluetooth/ath3k.c | 28 ++++++----
drivers/bluetooth/btmrvl_main.c | 2 +-
drivers/bluetooth/btrtl.c | 119 ++++++++++++++++++++++++++++------------
drivers/bluetooth/btusb.c | 10 ++++
drivers/bluetooth/hci_ath.c | 4 +-
drivers/bluetooth/hci_ll.c | 2 +-
net/bluetooth/hci_request.c | 6 +-
7 files changed, 118 insertions(+), 53 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2018-02-15 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 8:33 Johan Hedberg [this message]
2018-02-15 8:33 ` pull request: bluetooth-next 2018-02-15 Johan Hedberg
2018-02-15 20:44 ` 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=20180215083359.GA593@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.