From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] dcb59d: device: Add bearer info to Connected/Disconnected ...
Date: Fri, 20 Jun 2025 02:37:23 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/974159/000000-dcb59d@github.com> (raw)
Branch: refs/heads/974159
Home: https://github.com/bluez/bluez
Commit: dcb59d21c0d425d2bcffe251f6eb15e489151e29
https://github.com/bluez/bluez/commit/dcb59d21c0d425d2bcffe251f6eb15e489151e29
Author: Ye He <ye.he@amlogic.com>
Date: 2025-06-20 (Fri, 20 Jun 2025)
Changed paths:
M doc/org.bluez.Device.rst
M src/device.c
Log Message:
-----------
device: Add bearer info to Connected/Disconnected signals
This patch adds the Connected signals and updates the Disconnected signals
to use a dictionary instead of individual arguments, allowing additional
information to be conveyed in a backward-compatible way.
Specifically, a new "bearer" key is added to both signals to indicate the
transport type ("le" or "bredr"). This is useful in dual-mode scenarios
where it is necessary to distinguish between BR/EDR and LE connections.
The original Disconnected signal was introduced in BlueZ 5.82 and has not
seen widespread usage yet, so this change minimizes the risk of breaking
existing applications. By adding both signals to a dictionary-based
format now, future extensions can be added without requiring further API
changes.
Fixes: https://github.com/bluez/bluez/issues/1350
Signed-off-by: Ye He <ye.he@amlogic.com>
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-06-20 9:37 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/974159/000000-dcb59d@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