From: cochcoder <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e58f2b: shared/asha: send STOP without waiting for a response
Date: Mon, 12 Oct 2026 21:00:31 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1184353/000000-e58f2b@github.com> (raw)
Branch: refs/heads/1184353
Home: https://github.com/bluez/bluez
Commit: e58f2b24c46c62d200abacf4ac2d5c5b3d484bb9
https://github.com/bluez/bluez/commit/e58f2b24c46c62d200abacf4ac2d5c5b3d484bb9
Author: Kyle Pepper <cochcoder@proton.me>
Date: 2026-10-13 (Tue, 13 Oct 2026)
Changed paths:
M .gitignore
M Makefile.am
M src/shared/asha.c
A unit/test-asha-stop.c
Log Message:
-----------
shared/asha: send STOP without waiting for a response
STOP resets local state without consuming the ATT response. Use a Write
Command so an unresponsive renderer does not hold the request queue
until timeout.
Test command semantics, failure handling and peer STATUS notification.
Fixes: 9948168cca15 ("shared/asha: Don't wait for status notification on stop")
Assisted-by: OpenCode:gpt-6.1-sol
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-13 4:00 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/1184353/000000-e58f2b@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