From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] d4d636: error: Rename device error helper to match retval
Date: Tue, 01 Jul 2025 03:21:55 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/977659/000000-c2b027@github.com> (raw)
Branch: refs/heads/977659
Home: https://github.com/bluez/bluez
Commit: d4d636b22d08d70937febad2fcb0038ca32a8e68
https://github.com/bluez/bluez/commit/d4d636b22d08d70937febad2fcb0038ca32a8e68
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M src/device.c
M src/error.c
M src/error.h
Log Message:
-----------
error: Rename device error helper to match retval
Rename the helper to show that it outputs a string, and not an error
DbusMessage as the other functions do.
Commit: 660d04f0a95be83c1f8dc79e1ebe9ffcb62a7a14
https://github.com/bluez/bluez/commit/660d04f0a95be83c1f8dc79e1ebe9ffcb62a7a14
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M src/error.c
M src/error.h
Log Message:
-----------
error: Add helper to return DbusMessage errors from errno
This will allow us to start adding more precise errors instead of
"Failed" with a string if we're parsing an errno.
Commit: 2f6b814a499f347c15e36cd0d1fa327ea11d4d5d
https://github.com/bluez/bluez/commit/2f6b814a499f347c15e36cd0d1fa327ea11d4d5d
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M src/device.c
Log Message:
-----------
device: Use new DbusMessage error helper
Commit: 9b00d10c55113f75ab5684f0fdd00996a9ce4a80
https://github.com/bluez/bluez/commit/9b00d10c55113f75ab5684f0fdd00996a9ce4a80
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M src/error.c
M src/error.h
Log Message:
-----------
error: Make errno to string helpers private
We're not using them outside the error code itself.
Commit: 898da922298745920209885fa84afaf174a99e4d
https://github.com/bluez/bluez/commit/898da922298745920209885fa84afaf174a99e4d
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M doc/org.bluez.Device.rst
M src/device.c
M src/error.c
M src/error.h
Log Message:
-----------
device: Better error when no BR/EDR profiles can be connected to
Add a more precise error when there are no BR/EDR profiles to connect
to. This is useful when trying to connect to a particular device, and
there are no relevant profiles to connect to on the bearer.
Commit: d030c498000202554f2dab4413a809f7140f158a
https://github.com/bluez/bluez/commit/d030c498000202554f2dab4413a809f7140f158a
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M src/device.c
Log Message:
-----------
device: Better "Connect" debug
Output clearer debug information so that it's possible to follow the
decisions made by the bluetoothd daemon when a client such as
bluetoothctl or the GNOME Bluetooth settings ask it to connect to a
device.
Commit: c76080b99af6fe1d41c1bc34b6ed18eede4275e5
https://github.com/bluez/bluez/commit/c76080b99af6fe1d41c1bc34b6ed18eede4275e5
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M doc/org.bluez.Device.rst
M src/device.c
M src/error.c
M src/error.h
Log Message:
-----------
device: Better error when the link key is missing
Add a more precise error when the link key is missing for a
profile or device we're trying to connect to.
Commit: c2b027956baea12d9c6d9f1dd025a326617fcd56
https://github.com/bluez/bluez/commit/c2b027956baea12d9c6d9f1dd025a326617fcd56
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M doc/org.bluez.Device.rst
M src/device.c
M src/error.c
M src/error.h
Log Message:
-----------
device: Better error when the adapter is not powered
Compare: https://github.com/bluez/bluez/compare/d4d636b22d08%5E...c2b027956bae
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-01 10:21 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/977659/000000-c2b027@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