LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Marcel Holtmann <firstname.lastname@example.org>
To: Greg Kroah-Hartman <email@example.com>
Cc: Johan Hedberg <firstname.lastname@example.org>,
Sathish Narsimman <email@example.com>,
"David S. Miller" <firstname.lastname@example.org>,
Jakub Kicinski <email@example.com>,
"open list:NETWORKING [GENERAL]" <firstname.lastname@example.org>,
Subject: Re: [PATCH] Revert "Bluetooth: Update resolving list when updating whitelist"
Date: Sat, 3 Oct 2020 20:33:18 +0200 [thread overview]
Message-ID: <AABC2831-4E88-41A2-8A20-1BFC88895686@holtmann.org> (raw)
>>> This reverts commit 0eee35bdfa3b472cc986ecc6ad76293fdcda59e2 as it
>>> breaks all bluetooth connections on my machine.
>>> Cc: Marcel Holtmann <email@example.com>
>>> Cc: Sathish Narsimman <firstname.lastname@example.org>
>>> Fixes: 0eee35bdfa3b ("Bluetooth: Update resolving list when updating whitelist")
>>> Signed-off-by: Greg Kroah-Hartman <email@example.com>
>>> net/bluetooth/hci_request.c | 41 ++-----------------------------------
>>> 1 file changed, 2 insertions(+), 39 deletions(-)
>>> This has been bugging me for since 5.9-rc1, when all bluetooth devices
>>> stopped working on my desktop system. I finally got the time to do
>>> bisection today, and it came down to this patch. Reverting it on top of
>>> 5.9-rc7 restored bluetooth devices and now my input devices properly
>>> As it's almost 5.9-final, any chance this can be merged now to fix the
>> can you be specific what breaks since our guys and I also think the
>> ChromeOS guys have been testing these series of patches heavily.
> My bluetooth trackball does not connect at all. With this reverted, it
> all "just works".
> Same I think for a Bluetooth headset, can check that again if you really
> need me to, but the trackball is reliable here.
>> When you run btmon does it indicate any errors?
> How do I run it and where are the errors displayed?
you can do btmon -w trace.log and just let it run like tcdpump.
>> Do you have a chance to test net-next and see the LL Privacy there might have addressed this?
> Have a specific set of patches I can test? It wouldn't be good to have
> 5.9-final go out with this not working at all.
Of course not, but so far you are the only one reported a problem. Maybe you have some funky hardware in your machine that needs a quirk.
next prev parent reply other threads:[~2020-10-03 18:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 13:54 Greg Kroah-Hartman
2020-10-03 15:51 ` Marcel Holtmann
2020-10-03 16:07 ` Greg Kroah-Hartman
2020-10-03 18:33 ` Marcel Holtmann [this message]
2020-10-04 10:51 ` Greg Kroah-Hartman
2020-10-04 10:53 ` Greg Kroah-Hartman
2020-10-04 12:17 ` Bastien Nocera
2020-10-04 13:18 ` Greg Kroah-Hartman
2020-10-04 13:23 ` Bastien Nocera
2020-10-05 8:29 ` Greg Kroah-Hartman
2020-10-04 16:59 ` Marcel Holtmann
2020-10-05 8:36 ` Greg Kroah-Hartman
2020-10-05 12:19 ` Marcel Holtmann
2020-10-05 12:40 ` Greg Kroah-Hartman
2020-10-05 15:44 ` Marcel Holtmann
2020-10-05 16:11 ` Greg Kroah-Hartman
2020-10-05 17:14 ` Marcel Holtmann
2020-10-05 17:38 ` Greg Kroah-Hartman
2020-10-05 18:02 ` Greg Kroah-Hartman
2020-10-05 18:58 ` Marcel Holtmann
2020-10-07 13:23 ` Greg Kroah-Hartman
2020-10-07 13:40 ` Greg Kroah-Hartman
2020-10-07 13:43 ` Greg Kroah-Hartman
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [PATCH] Revert "Bluetooth: Update resolving list when updating whitelist"' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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).