From: Hitalo Souza <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 814e34: tools/sco-tester: Add test closing the socket befo...
Date: Thu, 08 Oct 2026 18:29:51 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1181897/000000-39fe2d@github.com> (raw)
Branch: refs/heads/1181897
Home: https://github.com/bluez/bluez
Commit: 814e3496a888f127826ad931f085391278c165b6
https://github.com/bluez/bluez/commit/814e3496a888f127826ad931f085391278c165b6
Author: Hitalo Souza <enghitalo@gmail.com>
Date: 2026-10-09 (Fri, 09 Oct 2026)
Changed paths:
M tools/sco-tester.c
Log Message:
-----------
tools/sco-tester: Add test closing the socket before the link is up
Add a test that closes the socket while the emulator holds the
Synchronous Connection Complete event of its setup, so that the kernel
aborts the connection before the link comes up. No connection takes the
link then, so the test expects the kernel to disconnect it, as the
controller would otherwise keep it and reject further setups for the
device.
eSCO CVSD - Close Before Complete
Assisted-by: Claude:claude-opus-5-5
Commit: 39fe2d600d0f3c8c96580cebf7bd75b44c40d483
https://github.com/bluez/bluez/commit/39fe2d600d0f3c8c96580cebf7bd75b44c40d483
Author: Hitalo Souza <enghitalo@gmail.com>
Date: 2026-10-09 (Fri, 09 Oct 2026)
Changed paths:
M tools/l2cap-tester.c
Log Message:
-----------
tools/l2cap-tester: Add tests closing the socket before the link is up
Add BR/EDR and LE client tests that close the socket while the emulator
holds the Connection Complete or LE Connection Complete event, so that
the kernel aborts the connection before the link comes up. No
connection takes the link then, so the tests expect the kernel to
disconnect it instead of leaving it up in the controller.
L2CAP BR/EDR Client - Close Before Complete
L2CAP LE Client - Close Before Complete
Assisted-by: Claude:claude-opus-5-5
Compare: https://github.com/bluez/bluez/compare/814e3496a888%5E...39fe2d600d0f
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-09 1:29 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/1181897/000000-39fe2d@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