[PATCH bluez] client: Fix issue of bearer info not printing correctly

[PATCH bluez] client: Fix issue of bearer info not printing correctly

[Ye He via B4 Relay]

From: Ye He <ye.he@amlogic.com>

The device proxy was incorrectly used when printing
bearer properties.

Signed-off-by: Ye He <ye.he@amlogic.com>
---
 client/main.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/client/main.c b/client/main.c
index 0a928efaa9bb0d2a806895ff8f8c0c7c0d2493bd..a3a46ca267b09fe54c2f3cfb723f3e72d03f699e 100644
--- a/client/main.c
+++ b/client/main.c
@@ -1894,9 +1894,9 @@ static void cmd_info(int argc, char *argv[])
 				      g_dbus_proxy_get_path(proxy),
 				      "org.bluez.Bearer.BREDR1");
 	if (bearer) {
-		print_property_with_label(proxy, "Paired", "BREDR.Paired");
-		print_property_with_label(proxy, "Bonded", "BREDR.Bonded");
-		print_property_with_label(proxy, "Connected",
+		print_property_with_label(bearer, "Paired", "BREDR.Paired");
+		print_property_with_label(bearer, "Bonded", "BREDR.Bonded");
+		print_property_with_label(bearer, "Connected",
 							"BREDR.Connected");
 	}
 
@@ -1904,9 +1904,9 @@ static void cmd_info(int argc, char *argv[])
 				      g_dbus_proxy_get_path(proxy),
 				      "org.bluez.Bearer.LE1");
 	if (bearer) {
-		print_property_with_label(proxy, "Paired", "LE.Paired");
-		print_property_with_label(proxy, "Bonded", "LE.Bonded");
-		print_property_with_label(proxy, "Connected", "LE.Connected");
+		print_property_with_label(bearer, "Paired", "LE.Paired");
+		print_property_with_label(bearer, "Bonded", "LE.Bonded");
+		print_property_with_label(bearer, "Connected", "LE.Connected");
 	}
 
 	return bt_shell_noninteractive_quit(EXIT_SUCCESS);

---
base-commit: 8a41ac3fde997137d374791a93a49d9a3abac0e0
change-id: 20251121-bearer-info-9091fa22c006

Best regards,
-- 
Ye He <ye.he@amlogic.com>

RE: [bluez] client: Fix issue of bearer info not printing correctly

[bluez.test.bot]

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1026231

---Test result---

Test Summary:
CheckPatch                    PENDING   0.28 seconds
GitLint                       PENDING   0.68 seconds
BuildEll                      PASS      20.26 seconds
BluezMake                     PASS      634.14 seconds
MakeCheck                     PASS      21.56 seconds
MakeDistcheck                 PASS      239.42 seconds
CheckValgrind                 PASS      298.84 seconds
CheckSmatch                   PASS      344.43 seconds
bluezmakeextell               PASS      180.67 seconds
IncrementalBuild              PENDING   0.32 seconds
ScanBuild                     PASS      982.55 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth

Re: [PATCH bluez] client: Fix issue of bearer info not printing correctly

[patchwork-bot+bluetooth]

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Fri, 21 Nov 2025 17:16:25 +0800 you wrote:
> From: Ye He <ye.he@amlogic.com>
> 
> The device proxy was incorrectly used when printing
> bearer properties.
> 
> Signed-off-by: Ye He <ye.he@amlogic.com>
> 
> [...]

Here is the summary with links:
  - [bluez] client: Fix issue of bearer info not printing correctly
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ae54731047cd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html