From: patchwork-bot+bluetooth@kernel.org
To: Jiajia Liu <liujiajia@kylinos.cn>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, brian.gix@intel.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
liujia6264@gmail.com
Subject: Re: [PATCH v2] Bluetooth: hci_event: fix simultaneous discovery stuck in FINDING
Date: Wed, 03 Jun 2026 17:50:07 +0000 [thread overview]
Message-ID: <178050900789.1520440.5604013251973902506.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260602070032.51248-1-liujiajia@kylinos.cn>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 2 Jun 2026 15:00:32 +0800 you wrote:
> When hci_inquiry_complete_evt is called between le_scan_disable and
> le_set_scan_enable_complete and no remote name needs to be resolved,
> the interleaved discovery with SIMULTANEOUS quirk gets stuck in
> DISCOVERY_FINDING. le_set_scan_enable_complete does not check inquiry
> state. No one sets DISCOVERY_STOPPED in this process.
>
> Add state check in le_set_scan_enable_complete and change state if
> the state is DISCOVERY_FINDING. Tested with AX201 (8087:0026) in Dell
> Vostro 13. Discovering disabled MGMT Event below is reported when
> running into the above condition.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: hci_event: fix simultaneous discovery stuck in FINDING
https://git.kernel.org/bluetooth/bluetooth-next/c/ad85ec7a145b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-03 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 7:00 Jiajia Liu
2026-06-02 14:40 ` Paul Menzel
2026-06-02 16:43 ` Luiz Augusto von Dentz
2026-06-02 21:53 ` Paul Menzel
2026-06-03 2:45 ` Jiajia Liu
2026-06-03 17:50 ` patchwork-bot+bluetooth [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=178050900789.1520440.5604013251973902506.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liujia6264@gmail.com \
--cc=liujiajia@kylinos.cn \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®