From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b5d015: src/device: Add Disconnected signal to propagate d...
Date: Mon, 19 May 2025 09:39:25 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/964261/000000-a651f6@github.com> (raw)
Branch: refs/heads/964261
Home: https://github.com/bluez/bluez
Commit: b5d015c03f0614beb9ad091a37aae69f68d87627
https://github.com/bluez/bluez/commit/b5d015c03f0614beb9ad091a37aae69f68d87627
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-05-19 (Mon, 19 May 2025)
Changed paths:
M src/adapter.c
M src/device.c
M src/device.h
Log Message:
-----------
src/device: Add Disconnected signal to propagate disconnection reason
Currently a client application is informed of the disconnection by the
update of the Connected property to false.
This sends a Disconnected signal with the disconnection reason before
the property is updated.
This helps client application to know the reason for the disconnection
and to take appropriate action.
Commit: 64d6e7e08f8c6f846ba94978dd0fcb7dfcc76dd4
https://github.com/bluez/bluez/commit/64d6e7e08f8c6f846ba94978dd0fcb7dfcc76dd4
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-05-19 (Mon, 19 May 2025)
Changed paths:
M doc/org.bluez.Device.rst
Log Message:
-----------
doc/device: Add Disconnected signal
Commit: a651f60bbd2b485bbb0f06bfb1511da13be444cf
https://github.com/bluez/bluez/commit/a651f60bbd2b485bbb0f06bfb1511da13be444cf
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2025-05-19 (Mon, 19 May 2025)
Changed paths:
M client/main.c
Log Message:
-----------
client: Display disconnection reason
The new org.bluez.Device1.Disconnected signal propagates the
disconnection reason.
Compare: https://github.com/bluez/bluez/compare/b5d015c03f06%5E...a651f60bbd2b
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-05-19 16:39 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/964261/000000-a651f6@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.