From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/3] test: functional: add mpris-proxy end-to-end tests
Date: Tue, 15 Sep 2026 20:50:04 +0000 [thread overview]
Message-ID: <178950540463.2270046.15143718818647294828.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1789430529.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 15 Sep 2026 03:07:17 +0300 you wrote:
> Add tests for:
>
> MPRIS -> local player -> AVRCP / MCP -> remote player -> MPRIS
>
> Connection and basic operations are tested on smoketest level.
>
> The code is LLM-assisted, with manual design and details input. I
> reviewed and tested the result.
>
> [...]
Here is the summary with links:
- [BlueZ,1/3] test: functional: add mpris-proxy BR/EDR test cases
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3e7fb4ac2e28
- [BlueZ,2/3] test: functional: deduce pairing bearer in shared fixtures
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=acab65d06795
- [BlueZ,3/3] test: functional: run mpris-proxy tests over LE via MCP
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e2ec6827f7be
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-15 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 0:07 [PATCH BlueZ 0/3] test: functional: add mpris-proxy end-to-end tests Pauli Virtanen
2026-09-15 0:07 ` [PATCH BlueZ 1/3] test: functional: add mpris-proxy BR/EDR test cases Pauli Virtanen
2026-09-15 1:55 ` test: functional: add mpris-proxy end-to-end tests bluez.test.bot
2026-09-15 0:07 ` [PATCH BlueZ 2/3] test: functional: deduce pairing bearer in shared fixtures Pauli Virtanen
2026-09-15 0:07 ` [PATCH BlueZ 3/3] test: functional: run mpris-proxy tests over LE via MCP Pauli Virtanen
2026-09-15 20:50 ` patchwork-bot+bluetooth [this message]
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=178950540463.2270046.15143718818647294828.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.