From: Daniel Beer <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] fa1f2e: sink: clean up outstanding AVDTP requests if the s...
Date: Mon, 28 Oct 2024 14:16:20 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/c009be-d7bb2a@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: fa1f2e5ee14dd740293fc5f491816cb185c6e7d7
https://github.com/bluez/bluez/commit/fa1f2e5ee14dd740293fc5f491816cb185c6e7d7
Author: Daniel Beer <daniel.beer@igorinstitute.com>
Date: 2024-10-28 (Mon, 28 Oct 2024)
Changed paths:
M profiles/audio/sink.c
Log Message:
-----------
sink: clean up outstanding AVDTP requests if the stream goes away
If the stream goes IDLE while we have an outstanding request, connect_id
stays non-zero and is never cleared via a completion callback. As a
consequence, the profile on this device will never be connected
successfully again until BlueZ restarts.
Commit: d7bb2abed626a979037a042c02b9a4027c6eb943
https://github.com/bluez/bluez/commit/d7bb2abed626a979037a042c02b9a4027c6eb943
Author: Daniel Beer <daniel.beer@igorinstitute.com>
Date: 2024-10-28 (Mon, 28 Oct 2024)
Changed paths:
M profiles/audio/source.c
Log Message:
-----------
source: clean up outstanding AVDTP requests if the stream goes away
If the stream goes IDLE while we have an outstanding request, connect_id
stays non-zero and is never cleared via a completion callback. As a
consequence, the profile on this device will never be connected
successfully again until BlueZ restarts.
Compare: https://github.com/bluez/bluez/compare/c009be5c5973...d7bb2abed626
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2024-10-28 21:16 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/master/c009be-d7bb2a@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;
as well as URLs for NNTP newsgroup(s).