From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 77cfff: device: Add btd_device_bdaddr_type_connected
Date: Mon, 14 Jul 2025 13:47:59 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/982213/000000-e40ecb@github.com> (raw)
Branch: refs/heads/982213
Home: https://github.com/bluez/bluez
Commit: 77cfff3ba001d10369c9844bf01379764758d3a0
https://github.com/bluez/bluez/commit/77cfff3ba001d10369c9844bf01379764758d3a0
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-07-14 (Mon, 14 Jul 2025)
Changed paths:
M src/device.c
M src/device.h
Log Message:
-----------
device: Add btd_device_bdaddr_type_connected
This adds btd_device_bdaddr_type_connected which can return the
connected state based on the address type.
Commit: 74009521222ddfd7c757ce40f03e5e07ea3fe489
https://github.com/bluez/bluez/commit/74009521222ddfd7c757ce40f03e5e07ea3fe489
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-07-14 (Mon, 14 Jul 2025)
Changed paths:
M Makefile.am
A doc/org.bluez.Bearer.BREDR.rst
A doc/org.bluez.Bearer.LE.rst
Log Message:
-----------
doc: Add org.bluez.Bearer.LE and org.bluez.Bearer.BREDR
This adds bearer specific interfaces so they can properly be operated
separately.
Fixes: https://github.com/bluez/bluez/issues/1350
Commit: 84e94e1a638c35d757ed6625840684fd2f7c0659
https://github.com/bluez/bluez/commit/84e94e1a638c35d757ed6625840684fd2f7c0659
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-07-14 (Mon, 14 Jul 2025)
Changed paths:
M Makefile.am
A src/bearer.c
A src/bearer.h
M src/device.c
Log Message:
-----------
bearer: Add initial implementation of org.bluez.Bearer.{BREDR, LE}
This adds initial implementation of org.bluez.Bearer{BREDR, LE}(5)
interfaces.
Commit: 8873ae3b92776df520d45e37f3f5d46656f982ac
https://github.com/bluez/bluez/commit/8873ae3b92776df520d45e37f3f5d46656f982ac
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-07-14 (Mon, 14 Jul 2025)
Changed paths:
M client/main.c
Log Message:
-----------
client: Add support for org.bluez.Bearer.{BREDR, LE}1
This adds support for printing properties related to
org.bluez.Bearer.{BREDR, LE}1:
> info XX:XX:XX:XX:XX:XX
...
BREDR.Paired: yes
BREDR.Bonded: yes
BREDR.Connected: no
LE.Paired: yes
LE.Bonded: yes
LE.Connected: no
...
[CHG] BREDR XX:XX:XX:XX:XX:XX Connected: yes
Commit: e40ecb4745442b0bc6c5e53616298531b08bf931
https://github.com/bluez/bluez/commit/e40ecb4745442b0bc6c5e53616298531b08bf931
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-07-14 (Mon, 14 Jul 2025)
Changed paths:
M client/main.c
Log Message:
-----------
client: Rework handling of Disconnected signal
Print with color the signal to indicate there is a change, also rework
the order of the parameters and use bearer specific suffix if the signal
comes from org.bluez.Bearer.*.
Compare: https://github.com/bluez/bluez/compare/77cfff3ba001%5E...e40ecb474544
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-14 20:48 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/982213/000000-e40ecb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.