From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v4 1/6] client/player: Split unicast and broadcast presets
Date: Wed, 13 Mar 2024 21:00:31 +0000 [thread overview]
Message-ID: <171036363148.351.6183402925919088516.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240313194400.1397477-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 13 Mar 2024 15:43:55 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Although their name matches unicast and broadcast are not actually the
> same when it comes to RTN and Max Latency, so this splits their settings
> into 2 presets tables and fix the values for broadcast.
> ---
> client/player.c | 115 +++++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 110 insertions(+), 5 deletions(-)
Here is the summary with links:
- [BlueZ,v4,1/6] client/player: Split unicast and broadcast presets
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e35f4583421c
- [BlueZ,v4,2/6] client/player: Use macros from lc3.h to define presets
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=cae922c63bd5
- [BlueZ,v4,3/6] shared/lc3: Add definition for broadcast configurations
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=47df60e8b21e
- [BlueZ,v4,4/6] client/player: Use QOS macros from lc3.h to define presets
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=25f42cfc4653
- [BlueZ,v4,5/6] client/player: Cleanup broadcast QoS
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3ad367874630
- [BlueZ,v4,6/6] bap: Add proper default for broadcast setup
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fffa21d084ec
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-03-13 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 19:43 [PATCH BlueZ v4 1/6] client/player: Split unicast and broadcast presets Luiz Augusto von Dentz
2024-03-13 19:43 ` [PATCH BlueZ v4 2/6] client/player: Use macros from lc3.h to define presets Luiz Augusto von Dentz
2024-03-13 19:43 ` [PATCH BlueZ v4 3/6] shared/lc3: Add definition for broadcast configurations Luiz Augusto von Dentz
2024-03-13 19:43 ` [PATCH BlueZ v4 4/6] client/player: Use QOS macros from lc3.h to define presets Luiz Augusto von Dentz
2024-03-13 19:43 ` [PATCH BlueZ v4 5/6] client/player: Cleanup broadcast QoS Luiz Augusto von Dentz
2024-03-13 19:44 ` [PATCH BlueZ v4 6/6] bap: Add proper default for broadcast setup Luiz Augusto von Dentz
2024-03-13 21:00 ` patchwork-bot+bluetooth [this message]
2024-03-13 23:49 ` [BlueZ,v4,1/6] client/player: Split unicast and broadcast presets bluez.test.bot
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=171036363148.351.6183402925919088516.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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.