From: Kirill Samburskiy <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 59ce83: audio/avrcp: Track TG and CT events separately
Date: Fri, 03 Apr 2026 06:19:41 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1076973/000000-59ce83@github.com> (raw)
Branch: refs/heads/1076973
Home: https://github.com/bluez/bluez
Commit: 59ce8354e6118f1a0456089773eeff87b163e29c
https://github.com/bluez/bluez/commit/59ce8354e6118f1a0456089773eeff87b163e29c
Author: Kirill Samburskiy <k.samburskiy@omp.ru>
Date: 2026-04-03 (Fri, 03 Apr 2026)
Changed paths:
M profiles/audio/avrcp.c
Log Message:
-----------
audio/avrcp: Track TG and CT events separately
Since we support both target and controller AVRCP roles, we need to
track events for each role separately to avoid confusing events that we
registered for notification from remote TG, and events that remote CT
registered for notification from us. This change is only relevant if
both sides support both CT and TG roles.
Fixes: https://github.com/bluez/bluez/issues/1997
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-03 13:19 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/1076973/000000-59ce83@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