From: raghava447 <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 07840e: profiles/audio: Support MCS fast seeking
Date: Mon, 31 Aug 2026 00:12:35 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1154163/000000-13b41e@github.com> (raw)
Branch: refs/heads/1154163
Home: https://github.com/bluez/bluez
Commit: 07840e3ab727f571b484e6e60c4b0a93ae7af81e
https://github.com/bluez/bluez/commit/07840e3ab727f571b484e6e60c4b0a93ae7af81e
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-08-31 (Mon, 31 Aug 2026)
Changed paths:
M profiles/audio/mcp.c
M profiles/audio/media.c
M profiles/audio/media.h
Log Message:
-----------
profiles/audio: Support MCS fast seeking
Commit: 510358a8a6f757e3ed0cbe74c1341554fac75ecd
https://github.com/bluez/bluez/commit/510358a8a6f757e3ed0cbe74c1341554fac75ecd
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-08-31 (Mon, 31 Aug 2026)
Changed paths:
M profiles/audio/mcp.c
Log Message:
-----------
profiles/audio: Support MCS track position writes
This is needed to Pass PTS GMCS/SR/SP/BV-02-C test.
Commit: 13b41e05092d60d623b68428223d7ad5196e7b36
https://github.com/bluez/bluez/commit/13b41e05092d60d623b68428223d7ad5196e7b36
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-08-31 (Mon, 31 Aug 2026)
Changed paths:
M src/shared/mcp.c
M unit/test-mcp.c
Log Message:
-----------
shared/mcp: Notify unsupported RFU opcodes
This is needed to Pass PTS GMCS/SR/SPE/BI-01-C test.
Compare: https://github.com/bluez/bluez/compare/07840e3ab727%5E...13b41e05092d
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-31 7:12 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/1154163/000000-13b41e@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