From: raghu447 <raghavendra.rao@collabora.com>
To: linux-bluetooth@vger.kernel.org
Cc: raghu447 <raghavendra.rao@collabora.com>
Subject: [PATCH 0/4] Add MCS fast seek and track position write support
Date: Fri, 4 Sep 2026 22:23:28 +0530 [thread overview]
Message-ID: <20260904165332.42046-1-raghavendra.rao@collabora.com> (raw)
In-Reply-To: <1654183666f442926c1301e1733567216b307981.camel@hadess.net>
These patches are needed to make MCS PTS tests pass.
raghavendra (4):
profiles/audio: Support MCS track position writes
profiles/audio: Support MCS fast seeking
shared/mcp: Notify unsupported RFU opcodes
unit/test-mcp: Test unsupported RFU opcode
profiles/audio/mcp.c | 71 ++++++++++++++++++++++++++++++++++++++++--
profiles/audio/media.c | 32 +++++++++++++++++++
profiles/audio/media.h | 1 +
src/shared/mcp.c | 2 +-
unit/test-mcp.c | 14 +++++++++
5 files changed, 117 insertions(+), 3 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2026-09-04 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 6:11 [BlueZ PATCH 0/3] Add MCS fast seek and track position write raghu447
2026-08-31 6:11 ` [BlueZ PATCH 1/3] profiles/audio: Support MCS fast seeking raghu447
2026-09-02 15:31 ` Luiz Augusto von Dentz
2026-08-31 6:11 ` [BlueZ PATCH 2/3] profiles/audio: Support MCS track position writes raghu447
2026-09-02 15:35 ` Luiz Augusto von Dentz
2026-09-03 8:19 ` Bastien Nocera
2026-09-04 16:53 ` raghu447 [this message]
2026-09-04 16:53 ` [PATCH 1/4] " raghu447
2026-09-04 17:51 ` Add MCS fast seek and track position write support bluez.test.bot
2026-09-04 16:53 ` [PATCH 2/4] profiles/audio: Support MCS fast seeking raghu447
2026-09-04 16:53 ` [PATCH 3/4] shared/mcp: Notify unsupported RFU opcodes raghu447
2026-09-04 16:53 ` [PATCH 4/4] unit/test-mcp: Test unsupported RFU opcode raghu447
2026-09-04 20:20 ` [PATCH 0/4] Add MCS fast seek and track position write support patchwork-bot+bluetooth
2026-08-31 6:11 ` [BlueZ PATCH 3/3] shared/mcp: Notify unsupported RFU opcodes raghu447
2026-09-02 15:36 ` Luiz Augusto von Dentz
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=20260904165332.42046-1-raghavendra.rao@collabora.com \
--to=raghavendra.rao@collabora.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