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 v2 0/2] Update BAP Broadcast Source state machine
Date: Thu, 23 May 2024 16:40:33 +0000 [thread overview]
Message-ID: <171648243349.722.2700809383644914438.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240523154754.39451-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, 23 May 2024 18:47:52 +0300 you wrote:
> Update BAP Broadcast Source state machine states to use BAP define states
> for source Idle, Config, Streaming, and an intermediary state enabling.
>
> Updated test-bap to.
>
> output from broadcast-source.bt
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] shared/bap: Update BAP Broadcast Source state machine
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5da00f712989
- [BlueZ,v2,2/2] bap: Update BAP Broadcast Source state machine states
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=75893035705d
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-05-23 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 15:47 [PATCH BlueZ v2 0/2] Update BAP Broadcast Source state machine Silviu Florian Barbulescu
2024-05-23 15:47 ` [PATCH BlueZ v2 1/2] shared/bap: " Silviu Florian Barbulescu
2024-05-23 18:13 ` bluez.test.bot
2024-05-23 15:47 ` [PATCH BlueZ v2 2/2] bap: Update BAP Broadcast Source state machine states Silviu Florian Barbulescu
2024-05-23 16: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=171648243349.722.2700809383644914438.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 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.