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-06-04
Date: Mon, 4 Jun 2018 12:15:32 +0200 [thread overview]
Message-ID: <20180604101532.GA8919@x1c> (raw)
[-- Attachment #1: Type: text/plain, Size: 2766 bytes --]
Hi Dave,
Here's one last bluetooth-next pull request for the 4.18 kernel:
- New USB device IDs for Realtek 8822BE and 8723DE
- reset/resume fix for Dell Inspiron 5565
- Fix HCI_UART_INIT_PENDING flag behavior
- Fix patching behavior for some ATH3012 models
- A few other minor cleanups & fixes
Please let me know if there are any issues pulling. Thanks.
Johan
---
The following changes since commit 874fcf1de613ad7b3cecf8a9cfe806fe7c2e3c68:
Merge tag 'mlx5e-updates-2018-05-25' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux (2018-05-29 09:45:13 -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 1cd2fabf4bdcf95eda6a1bcebc4a0a965509da36:
Bluetooth: btusb: Add additional device ID for RTL8822BE (2018-05-30 15:45:01 +0200)
----------------------------------------------------------------
Andy Shevchenko (2):
Bluetooth: Re-use kstrtobool_from_user()
Bluetooth: btmrvl: Re-use kstrtol_from_user()
Arend van Spriel (1):
Bluetooth: btmrvl: support sysfs initiated firmware coredump
Artiom Vaskov (1):
Bluetooth: btusb: Add additional device ID for RTL8822BE
Hans de Goede (4):
Bluetooth: btusb: Add Dell Inspiron 5565 to btusb_needs_reset_resume_table
Bluetooth: hci_uart: Restore hci_dev->flush callback on open()
Bluetooth: hci_serdev: Move serdev_device_close/open into common hci_serdev code
Bluetooth: hci_serdev: Fix HCI_UART_INIT_PENDING not working
Jian-Hong Pan (1):
Bluetooth: btusb: Add a new Realtek 8723DE ID 2ff8:b011
Takashi Iwai (1):
Bluetooth: btusb: Apply QCA Rome patches for some ATH3012 models
Thierry Escande (1):
Bluetooth: hci_qca: Fix "Sleep inside atomic section" warning
Vaibhav Murkute (1):
Bluetooth: hci_serdev: Removed unnecessary curly braces
drivers/bluetooth/btmrvl_debugfs.c | 55 +++-----------------------------------
drivers/bluetooth/btmrvl_drv.h | 2 --
drivers/bluetooth/btmrvl_main.c | 6 -----
drivers/bluetooth/btmrvl_sdio.c | 11 +++++---
drivers/bluetooth/btusb.c | 43 ++++++++++++++++++++++++-----
drivers/bluetooth/hci_bcm.c | 10 +------
drivers/bluetooth/hci_ldisc.c | 22 ++++++++-------
drivers/bluetooth/hci_ll.c | 3 ---
drivers/bluetooth/hci_nokia.c | 3 ---
drivers/bluetooth/hci_qca.c | 2 +-
drivers/bluetooth/hci_serdev.c | 32 ++++++++++++++--------
drivers/bluetooth/hci_uart.h | 1 +
net/bluetooth/hci_core.c | 23 +++++-----------
net/bluetooth/hci_debugfs.c | 24 ++++++-----------
net/bluetooth/smp.c | 12 +++------
15 files changed, 102 insertions(+), 147 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2018-06-04 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 10:15 Johan Hedberg [this message]
2018-06-04 21:22 ` pull request: bluetooth-next 2018-06-04 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=20180604101532.GA8919@x1c \
--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).