Re: [Regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable again with kernel 6.0 #forregzbot

[Thorsten Leemhuis <regressions@leemhuis.info>]

[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]

[TLDR: I'm adding this regression report to the list of tracked
regressions; all text from me you find below is based on a few templates
paragraphs you might have encountered already already in similar form.]

Hi, this is your Linux kernel regression tracker.

On 24.10.22 23:11, Jack wrote:
> Cheap USB BT dongles that are bad clones of CSR  "ID 0a12:0001 Cambridge
> Silicon Radio, Ltd Bluetooth Dongle (HCI mode)" have had historic
> problems, due to various bad behaviors.  See [Bug 60824]
> [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle
> unusable (https://bugzilla.kernel.org/show_bug.cgi) for more details and
> background.  The patch in that bug was initially mainlined in 5.9, and
> underwent several revisions since then.  It has continued to work
> through all of the 5.19 series, but it does not work with any of the 6.0
> kernels.
> [...]

Thanks for the report. To be sure below issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
tracking bot:

#regzbot ^introduced 766ae2422b4312
#regzbot title net: bluetooth: Cambridge Silicon Radio, Ltd Bluetooth
Dongle unusable again with kernel 6.0
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
https://linux-regtracking.leemhuis.info/tracked-regression/

Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (the mail this one replies to), as explained for
in the Linux kernel's documentation; above webpage explains why this is
important for tracked regressions.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.