From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v3 1/2] bap: use MediaEndpoint related properties consistently
Date: Tue, 03 Oct 2023 23:20:29 +0000 [thread overview]
Message-ID: <169637522929.21629.18022470109434488634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <530fedd2233740d401c67bc1470756c86cb578a2.1696360700.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, 3 Oct 2023 22:19:03 +0300 you wrote:
> Use the documented name "MaximumLatency" for the MediaEndpoint QoS
> Max_Transport_Latency field, in SelectProperties input parameters and
> expected client MediaEndpoint properties.
>
> Put QoS fields to a "QoS" dict in SelectProperties input.
>
> Fix typoed ppd_min -> ppd_max in SelectProperties input.
>
> [...]
Here is the summary with links:
- [BlueZ,v3,1/2] bap: use MediaEndpoint related properties consistently
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5e582e34e392
- [BlueZ,v3,2/2] doc: clarify org.bluez.MediaEndpoint documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6683305d827a
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:[~2023-10-03 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 19:19 [PATCH BlueZ v3 1/2] bap: use MediaEndpoint related properties consistently Pauli Virtanen
2023-10-03 19:19 ` [PATCH BlueZ v3 2/2] doc: clarify org.bluez.MediaEndpoint documentation Pauli Virtanen
2023-10-03 20:50 ` [BlueZ,v3,1/2] bap: use MediaEndpoint related properties consistently bluez.test.bot
2023-10-03 23:20 ` 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=169637522929.21629.18022470109434488634.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.