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 v3 0/7] Add support for multiple BISes on the bcast source
Date: Wed, 21 Feb 2024 19:40:31 +0000 [thread overview]
Message-ID: <170854443182.27968.17013966618823039081.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240215212356.310301-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 Thu, 15 Feb 2024 23:23:49 +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,v3,1/7] bap: Remove set lpac user data at bcast ep register
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c5f1c5ba0e8d
- [BlueZ,v3,2/7] bap: Split bap_state and bap_connecting in two functions
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5629f4784a4d
- [BlueZ,v3,3/7] shared/bap: Generate one BIS BASE for
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a16c2ccf9c25
- [BlueZ,v3,4/7] shared/bap: Add state in stream struct for bcast source
(no matching commit)
- [BlueZ,v3,5/7] shared/bap: Check state of all streams with same BIG ID
(no matching commit)
- [BlueZ,v3,6/7] shared/bap: Add support to create stream for bcast source
(no matching commit)
- [BlueZ,v3,7/7] bap: Set generated BASE on all setups from the same BIG
(no matching commit)
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-21 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 21:23 [PATCH BlueZ v3 0/7] Add support for multiple BISes on the bcast source Silviu Florian Barbulescu
2024-02-15 21:23 ` [PATCH BlueZ v3 1/7] bap: Remove set lpac user data at bcast ep register Silviu Florian Barbulescu
2024-02-15 23:49 ` Add support for multiple BISes on the bcast source bluez.test.bot
2024-02-15 21:23 ` [PATCH BlueZ v3 2/7] bap: Split bap_state and bap_connecting in two functions Silviu Florian Barbulescu
2024-02-15 21:23 ` [PATCH BlueZ v3 3/7] shared/bap: Generate one BIS BASE for Silviu Florian Barbulescu
2024-02-15 21:23 ` [PATCH BlueZ v3 4/7] shared/bap: Add state in stream struct for bcast source Silviu Florian Barbulescu
2024-02-20 19:10 ` Luiz Augusto von Dentz
2024-02-15 21:23 ` [PATCH BlueZ v3 5/7] shared/bap: Check state of all streams with same BIG ID Silviu Florian Barbulescu
2024-02-15 21:23 ` [PATCH BlueZ v3 6/7] shared/bap: Add support to create stream for bcast source Silviu Florian Barbulescu
2024-02-15 21:23 ` [PATCH BlueZ v3 7/7] bap: Set generated BASE on all setups from the same BIG Silviu Florian Barbulescu
2024-02-21 19:40 ` 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=170854443182.27968.17013966618823039081.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).