From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] d8b0b4: device: Add bearer info to Connected/Disconnected ...
Date: Tue, 17 Jun 2025 20:35:05 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/973184/000000-d8b0b4@github.com> (raw)
Branch: refs/heads/973184
Home: https://github.com/bluez/bluez
Commit: d8b0b486b9130d257c21e7ffc0c6085df09e153e
https://github.com/bluez/bluez/commit/d8b0b486b9130d257c21e7ffc0c6085df09e153e
Author: Ye He <ye.he@amlogic.com>
Date: 2025-06-18 (Wed, 18 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 add a new Connected(string bearer) signal to indicate which transport
(LE or BR/EDR) has connected. Also extend the Disconnected signal to include
a bearer argument.
This allows applications to distinguish transport-specific connection
events in dual-mode scenarios.
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-18 3:35 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/973184/000000-d8b0b4@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;
as well as URLs for NNTP newsgroup(s).