From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 45747c: tools/l2cap-tester: add tests changing BT_SECURITY...
Date: Tue, 11 Aug 2026 13:56:45 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/690c16-10df0b@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 45747c6d0c853e1d711f24d1e7dc85a99d085925
https://github.com/bluez/bluez/commit/45747c6d0c853e1d711f24d1e7dc85a99d085925
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-08-11 (Tue, 11 Aug 2026)
Changed paths:
M tools/l2cap-tester.c
Log Message:
-----------
tools/l2cap-tester: add tests changing BT_SECURITY after connecting
Add tests that change BT_SECURITY value after connection established:
L2CAP BR/EDR Client PIN Code Change Sec - Success
L2CAP LE Client Change Sec - Success
L2CAP LE ATT Client Change Sec - Success
L2CAP LE EATT Client Change Sec - Success
Commit: ea77a7229c76a88e348c502a66ce500278cfa868
https://github.com/bluez/bluez/commit/ea77a7229c76a88e348c502a66ce500278cfa868
Author: z4pdy <305461556+z4pdy@users.noreply.github.com>
Date: 2026-08-11 (Tue, 11 Aug 2026)
Changed paths:
M client/main.c
Log Message:
-----------
client: Avoid scan prompt when discovery is already active
Check the adapter's Discovering property before prompting the user
to start scanning. This avoids prompting to scan when discovery is
already in progress, which previously resulted
in an org.bluez.Error.InProgress error.
Changes in v2:
- Move variable declarations to the beginning of cmd_connect()
to fix the ISO C90 build failure.
Commit: 10df0bb748449ba00ffe04fc4d77f4d287b97161
https://github.com/bluez/bluez/commit/10df0bb748449ba00ffe04fc4d77f4d287b97161
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-08-11 (Tue, 11 Aug 2026)
Changed paths:
M emulator/main.c
M emulator/server.c
M emulator/server.h
Log Message:
-----------
emulator: btvirt: support debug for -s socket server
Support btdev debug -d when using socket server -s.
$ btvirt -d -s
Bluetooth emulator ver 5.87
Request for /tmp/bt-server-bredrle
bredrle: host10: > 01 01 10 00 ....
bredrle: host10: command 0x1001
bredrle: host10: event 0x0e opcode 0x1001
...
Compare: https://github.com/bluez/bluez/compare/690c16df6067...10df0bb74844
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-11 20:56 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/690c16-10df0b@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