From: patchwork-bot+bluetooth@kernel.org
To: Vlad Pruteanu <vlad.pruteanu@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, claudia.rosu@nxp.com,
mihai-octavian.urzica@nxp.com, silviu.barbulescu@nxp.com,
iulia.tanasescu@nxp.com, andrei.istodorescu@nxp.com
Subject: Re: [PATCH BlueZ v4 0/1] bap: Use defer setup when syncing to a BIS source
Date: Tue, 12 Sep 2023 18:50:26 +0000 [thread overview]
Message-ID: <169454462653.13260.2986968091954754161.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230912065526.1217334-1-vlad.pruteanu@nxp.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 12 Sep 2023 09:55:25 +0300 you wrote:
> This commit uses the newly added bt_io_bcast_accept function from
> btio.c to implement the defer setup for the BIS sync process.
> Now, information from the BIG Info advertising report can be
> used when sending the BIG Create Sync command.
>
> Vlad Pruteanu (1):
> bap: Use defer setup when syncing to a BIS source
>
> [...]
Here is the summary with links:
- [BlueZ,v4,1/1] bap: Use defer setup when syncing to a BIS source
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=feadcbbed50d
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:[~2023-09-12 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 6:55 [PATCH BlueZ v4 0/1] bap: Use defer setup when syncing to a BIS source Vlad Pruteanu
2023-09-12 6:55 ` [PATCH BlueZ v4 1/1] " Vlad Pruteanu
2023-09-12 8:11 ` bluez.test.bot
2023-09-12 18: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=169454462653.13260.2986968091954754161.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=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.