Re: [RFC PATCH 0/2] Bluetooth: detect broken extended scan instead of guessing by chip id

"Kamil Serwus" <[email protected]>
Newsgroups dev.linux.lists.regressions,org.kernel.vger.linux-bluetooth,org.kernel.vger.linux-kernel
Message-ID <[email protected]> 
Hi Thorsten,

> Would you maybe be willing to submit a revert?

Yes, sending it now with Cc: stable so it can reach 7.1.y and 6.18.y.

It does put Alexej's dongle (0bda:a728) back to logging repeated -EBUSY
on extended scan - noisy, but usable, unlike the current state on mine.
The RFC series stays on the list for the proper fix; Alexej, testing it
would still be welcome.

Kamil
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.