netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2018-03-05
Date: Mon, 5 Mar 2018 14:29:12 +0200	[thread overview]
Message-ID: <20180305122912.GA12251@x1c.lan> (raw)

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

Hi Dave,

Here are a few more Bluetooth fixes for the 4.16 kernel:

 - btusb: reset/resume fixes for Yoga 920 and Dell OptiPlex 3060
 - Fix for missing encryption refresh with the Security Manager protocol

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

Johan

---
The following changes since commit 773daa3caf5d3f87fdb1ab43e9c1b367a38fa394:

  net: ipv4: avoid unused variable warning for sysctl (2018-03-01 13:38:22 -0500)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git for-upstream

for you to fetch changes up to 64e759f58f128730b97a3c3a26d283c075ad7c86:

  Bluetooth: Fix missing encryption refresh on Security Request (2018-03-01 19:55:56 +0100)

----------------------------------------------------------------
Hans de Goede (1):
      Bluetooth: btusb: Remove Yoga 920 from the btusb_needs_reset_resume_table

Kai-Heng Feng (1):
      Bluetooth: btusb: Add Dell OptiPlex 3060 to btusb_needs_reset_resume_table

Szymon Janc (1):
      Bluetooth: Fix missing encryption refresh on Security Request

 drivers/bluetooth/btusb.c | 6 +++---
 net/bluetooth/smp.c       | 8 +++++++-
 2 files changed, 10 insertions(+), 4 deletions(-)

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

             reply	other threads:[~2018-03-05 12:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 12:29 Johan Hedberg [this message]
2018-03-07 15:51 ` pull request: bluetooth 2018-03-05 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=20180305122912.GA12251@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).