From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 9dc877: client: Fix issue of bearer info not printing corr...
Date: Fri, 21 Nov 2025 01:21:26 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1026231/000000-9dc877@github.com> (raw)
Branch: refs/heads/1026231
Home: https://github.com/bluez/bluez
Commit: 9dc8772297ba47afa23adbfef0f380f1c28d6b71
https://github.com/bluez/bluez/commit/9dc8772297ba47afa23adbfef0f380f1c28d6b71
Author: Ye He <ye.he@amlogic.com>
Date: 2025-11-21 (Fri, 21 Nov 2025)
Changed paths:
M client/main.c
Log Message:
-----------
client: Fix issue of bearer info not printing correctly
The device proxy was incorrectly used when printing
bearer properties.
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-11-21 9: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/1026231/000000-9dc877@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