From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 9372cc: org.bluez.Bearer: Add Role property
Date: Fri, 09 Oct 2026 12:53:18 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1182613/000000-2957df@github.com> (raw)
Branch: refs/heads/1182613
Home: https://github.com/bluez/bluez
Commit: 9372cc1782e0e10cd7d064c10bed1815af47338f
https://github.com/bluez/bluez/commit/9372cc1782e0e10cd7d064c10bed1815af47338f
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-09 (Fri, 09 Oct 2026)
Changed paths:
M doc/org.bluez.Bearer.LE.rst
Log Message:
-----------
org.bluez.Bearer: Add Role property
This adds Role property to org.bluez.Bearer.LE1 which indicates whether
the remote device is the central or the peripheral of the current LE
connection, so applications can tell a central that connected to the
adapter from a peripheral the adapter connected to.
Assisted-by: Claude:claude-opus-5.5
Commit: 25996bf0fdf1fc3bec723ef9a4a09f155407da61
https://github.com/bluez/bluez/commit/25996bf0fdf1fc3bec723ef9a4a09f155407da61
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-09 (Fri, 09 Oct 2026)
Changed paths:
M src/bearer.c
M src/device.c
M src/device.h
Log Message:
-----------
bearer: Add Role property
This implements Role property for the LE bearer using the initiator
flag of the Device Connected event, which the kernel sets when the
adapter created the connection as central, and emits PropertiesChanged
along with Connected.
Assisted-by: Claude:claude-opus-5.5
Commit: e628b057bb09c36b515aefd46bcf33b6f2631e78
https://github.com/bluez/bluez/commit/e628b057bb09c36b515aefd46bcf33b6f2631e78
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-09 (Fri, 09 Oct 2026)
Changed paths:
M client/main.c
Log Message:
-----------
client: Print LE.Role in info
This prints the Role property of the LE bearer with the likes of info
command:
bluetoothctl> info <addr>
...
LE.Connected: yes
LE.Connectable: yes
LE.Role: central
Assisted-by: Claude:claude-opus-5.5
Commit: 4e2ea23b375b1db21ff57dda4d95808309dfc00a
https://github.com/bluez/bluez/commit/4e2ea23b375b1db21ff57dda4d95808309dfc00a
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-09 (Fri, 09 Oct 2026)
Changed paths:
M Makefile.am
A doc/functional-bearer.rst
M doc/functional-testing.rst
Log Message:
-----------
doc: Add functional-bearer documentation
Document the bearer functional tests, where two hosts connect or pair
over LE or BR/EDR and each checks the org.bluez.Bearer.LE1 and
org.bluez.Bearer.BREDR1 properties of the device object it has for the
other:
- Connected and Role on both sides of an LE connection, and the
Disconnected signal with its reason on both sides
- Connectable for a connectable advertiser and for a broadcaster
- Paired, Bonded and Connected after LE and BR/EDR pairing, Role being
only reported for LE
Assisted-by: Claude:claude-opus-5.5
Commit: 2957df116f671d1ca6efc22846045011bcc5eeeb
https://github.com/bluez/bluez/commit/2957df116f671d1ca6efc22846045011bcc5eeeb
Author: Kevin Dewald <kevin@simpleble.org>
Date: 2026-10-09 (Fri, 09 Oct 2026)
Changed paths:
A test/functional/test_bearer.py
Log Message:
-----------
test: functional: add bearer tests
Add tests where host0 connects to or pairs with host1 over LE or
BR/EDR, and both hosts check the properties and the Disconnected
signal of the bearer interfaces of the device object they have for the
other, including the LE Role of each side of the connection.
See doc/functional-bearer.rst for details.
Assisted-by: Claude:claude-opus-5.5
Compare: https://github.com/bluez/bluez/compare/9372cc1782e0%5E...2957df116f67
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-09 19:53 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/1182613/000000-2957df@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