From: patchwork-bot+bluetooth@kernel.org
To: Silviu Florian Barbulescu <silviu.barbulescu@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, mihai-octavian.urzica@nxp.com,
vlad.pruteanu@nxp.com, andrei.istodorescu@nxp.com,
luiz.dentz@gmail.com, iulia.tanasescu@nxp.com
Subject: Re: [PATCH BlueZ v4 0/5] Add support for multiple BISes on the bcast source
Date: Tue, 27 Feb 2024 14:30:31 +0000 [thread overview]
Message-ID: <170904423110.32001.11874673824840523535.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240223164813.66484-1-silviu.barbulescu@nxp.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 23 Feb 2024 18:48:08 +0200 you wrote:
> This patch adds support for multiple BISes in broadcast sources.
>
> Example commands:
> Create a local endpoint and an endpoint for BIS1:
> endpoint.register 00001852-0000-1000-8000-00805f9b34fb 0x06
> [/local/endpoint/ep0] Auto Accept (yes/no): y
> [/local/endpoint/ep0] Max Transports (auto/value): a
> [/local/endpoint/ep0] Locations: 0x03
> [/local/endpoint/ep0] Supported Context (value): 0
>
> [...]
Here is the summary with links:
- [BlueZ,v4,1/5] shared/bap: Fix endpoint dir for the bcast source
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8552e06b6617
- [BlueZ,v4,2/5] shared/bap: Add state in stream struct for bcast source
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b4f9a9fd7ed2
- [BlueZ,v4,3/5] shared/bap: Add support to create a stream for bcast src
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6ea7f481094c
- [BlueZ,v4,4/5] bap: Add a callback to create a new stream
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=dd57562760e4
- [BlueZ,v4,5/5] bap: Set generated BASE on all setups from the same BIG
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=92f3ed187904
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:[~2024-02-27 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 16:48 [PATCH BlueZ v4 0/5] Add support for multiple BISes on the bcast source Silviu Florian Barbulescu
2024-02-23 16:48 ` [PATCH BlueZ v4 1/5] shared/bap: Fix endpoint dir for " Silviu Florian Barbulescu
2024-02-23 18:51 ` Add support for multiple BISes on " bluez.test.bot
2024-02-23 16:48 ` [PATCH BlueZ v4 2/5] shared/bap: Add state in stream struct for " Silviu Florian Barbulescu
2024-02-23 16:48 ` [PATCH BlueZ v4 3/5] shared/bap: Add support to create a stream for bcast src Silviu Florian Barbulescu
2024-02-23 16:48 ` [PATCH BlueZ v4 4/5] bap: Add a callback to create a new stream Silviu Florian Barbulescu
2024-02-23 16:48 ` [PATCH BlueZ v4 5/5] bap: Set generated BASE on all setups from the same BIG Silviu Florian Barbulescu
2024-02-27 14:30 ` 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=170904423110.32001.11874673824840523535.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=andrei.istodorescu@nxp.com \
--cc=iulia.tanasescu@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=mihai-octavian.urzica@nxp.com \
--cc=silviu.barbulescu@nxp.com \
--cc=vlad.pruteanu@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).