From: Andreas Glinserer <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e9bac1: src/adapter: add timeout for missing discovery
Date: Fri, 12 Sep 2025 03:43:36 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1001717/000000-e9bac1@github.com> (raw)
Branch: refs/heads/1001717
Home: https://github.com/bluez/bluez
Commit: e9bac13f371845d3e38d7040862fd092c17f40b0
https://github.com/bluez/bluez/commit/e9bac13f371845d3e38d7040862fd092c17f40b0
Author: Andreas Glinserer <andreas.glinserer@canonical.com>
Date: 2025-09-12 (Fri, 12 Sep 2025)
Changed paths:
M src/adapter.c
Log Message:
-----------
src/adapter: add timeout for missing discovery
Add a timeout to detect when the controller stops sending discovery
events. Without this, the system silently discovering new devices
and the scan list gradually empties due to DEFAULT_TEMPORARY_TIMEOUT.
When the timeout triggers, issue MGMT_OP_STOP_DISCOVERY to restart the
event loop and resume discovery.
Link: https://github.com/bluez/bluez/issues/1554
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-09-12 10:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1001717/000000-e9bac1@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.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