All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kamil Serwus" <kserwus@gmail.com>
To: "Thorsten Leemhuis" <regressions@leemhuis.info>,
	"Kamil Serwus" <kserwus@gmail.com>,
	<linux-bluetooth@vger.kernel.org>
Cc: "Alexej Sidorenko" <alexej@sidorenko.cz>,
	"Luiz Augusto von Dentz" <luiz.dentz@gmail.com>,
	"Marcel Holtmann" <marcel@holtmann.org>,
	<regressions@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/2] Bluetooth: detect broken extended scan instead of guessing by chip id
Date: Sun, 23 Aug 2026 12:27:01 +0200	[thread overview]
Message-ID: <DKW92HEH75C6.24ZHHWR1XJ46C@gmail.com> (raw)
In-Reply-To: <68dc7fba-ddda-4505-bdaf-4bb7af2df44e@leemhuis.info>

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

      reply	other threads:[~2026-08-23 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 14:11 [RFC PATCH 0/2] Bluetooth: detect broken extended scan instead of guessing by chip id Kamil Serwus
2026-08-22 14:11 ` [RFC PATCH 1/2] Bluetooth: hci_sync: latch broken ext scan on Command Disallowed Kamil Serwus
2026-08-22 14:49   ` Bluetooth: detect broken extended scan instead of guessing by chip id bluez.test.bot
2026-08-22 14:11 ` [RFC PATCH 2/2] Bluetooth: btrtl: drop the blanket RTL8761B extended scan quirk Kamil Serwus
2026-08-23  9:39 ` [RFC PATCH 0/2] Bluetooth: detect broken extended scan instead of guessing by chip id Thorsten Leemhuis
2026-08-23 10:27   ` Kamil Serwus [this message]

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=DKW92HEH75C6.24ZHHWR1XJ46C@gmail.com \
    --to=kserwus@gmail.com \
    --cc=alexej@sidorenko.cz \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.