diff options
author | Hans de Goede <hdegoede@redhat.com> | 2018-02-28 11:57:50 +0100 |
---|---|---|
committer | Marcel Holtmann <marcel@holtmann.org> | 2018-03-01 19:55:56 +0100 |
commit | f0e8c61110c2c85903b136ba070daf643a8b6842 (patch) | |
tree | ead98a68fd12ac1fa68bdd80b97833d503a33da0 /net/bluetooth/smp.c | |
parent | net: ipv4: avoid unused variable warning for sysctl (diff) | |
download | linux-dev-f0e8c61110c2c85903b136ba070daf643a8b6842.tar.xz linux-dev-f0e8c61110c2c85903b136ba070daf643a8b6842.zip |
Bluetooth: btusb: Remove Yoga 920 from the btusb_needs_reset_resume_table
Commit 1fdb92697469 ("Bluetooth: btusb: Use DMI matching for QCA
reset_resume quirking"), added the Lenovo Yoga 920 to the
btusb_needs_reset_resume_table.
Testing has shown that this is a false positive and the problems where
caused by issues with the initial fix: commit fd865802c66b ("Bluetooth:
btusb: fix QCA Rome suspend/resume"), which has already been reverted.
So the QCA Rome BT in the Yoga 920 does not need a reset-resume quirk at
all and this commit removes it from the btusb_needs_reset_resume_table.
Note that after this commit the btusb_needs_reset_resume_table is now
empty. It is kept around on purpose, since this whole series of commits
started for a reason and there are actually broken platforms around,
which need to be added to it.
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1514836
Fixes: 1fdb92697469 ("Bluetooth: btusb: Use DMI matching for QCA ...")
Cc: stable@vger.kernel.org
Cc: Brian Norris <briannorris@chromium.org>
Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>
Tested-by: Kevin Fenzi <kevin@scrye.com>
Suggested-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Reviewed-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth/smp.c')
0 files changed, 0 insertions, 0 deletions