From: patchwork-bot+bluetooth@kernel.org
To: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, claudia.rosu@nxp.com,
mihai-octavian.urzica@nxp.com, silviu.barbulescu@nxp.com,
vlad.pruteanu@nxp.com, andrei.istodorescu@nxp.com,
luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ 0/6] Add new BAP BSRC/SCC tests
Date: Mon, 03 Jun 2024 13:50:30 +0000 [thread overview]
Message-ID: <171742263036.17260.11390200178623096049.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240527075422.18953-1-iulia.tanasescu@nxp.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 27 May 2024 10:54:16 +0300 you wrote:
> This patch adds BAP unit tests for Broadcast Source stream
> establishment (BAP/BSRC/SCC/BV-35-C [Establishes Broadcast] - page 175),
> stream disable (BAP/BSRC/SCC/BV-36-C [Disables Broadcast] - page 176) and
> stream release (BAP/BSRC/SCC/BV-37-C [Releases Broadcast] - page 176).
>
> This patch also adds shared/bap fixes regarding broadcast stream
> management, required for successful test implementation.
>
> [...]
Here is the summary with links:
- [BlueZ,1/6] shared/bap: Remove DISABLING case from bcast state cb
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=491e5b353700
- [BlueZ,2/6] shared/bap: Fix potential stream access after free
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=af2873b26912
- [BlueZ,3/6] test-bap: Update bsrc_state to just handle CONFIG state
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6cb268f47f47
- [BlueZ,4/6] test-bap: Add Broadcast Source Establish test
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=bb30b1990154
- [BlueZ,5/6] test-bap: Add Broadcast Source Disable test
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=06a905d6b8c8
- [BlueZ,6/6] test-bap: Add Broadcast Source Release test
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3f747788c1b1
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-06-03 13:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 7:54 [PATCH BlueZ 0/6] Add new BAP BSRC/SCC tests Iulia Tanasescu
2024-05-27 7:54 ` [PATCH BlueZ 1/6] shared/bap: Remove DISABLING case from bcast state cb Iulia Tanasescu
2024-05-27 11:54 ` Add new BAP BSRC/SCC tests bluez.test.bot
2024-05-27 7:54 ` [PATCH BlueZ 2/6] shared/bap: Fix potential stream access after free Iulia Tanasescu
2024-05-27 7:54 ` [PATCH BlueZ 3/6] test-bap: Update bsrc_state to just handle CONFIG state Iulia Tanasescu
2024-05-27 7:54 ` [PATCH BlueZ 4/6] test-bap: Add Broadcast Source Establish test Iulia Tanasescu
2024-05-27 7:54 ` [PATCH BlueZ 5/6] test-bap: Add Broadcast Source Disable test Iulia Tanasescu
2024-05-27 7:54 ` [PATCH BlueZ 6/6] test-bap: Add Broadcast Source Release test Iulia Tanasescu
2024-05-31 17:17 ` [PATCH BlueZ 0/6] Add new BAP BSRC/SCC tests Luiz Augusto von Dentz
2024-06-03 13: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=171742263036.17260.11390200178623096049.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=andrei.istodorescu@nxp.com \
--cc=claudia.rosu@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 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.