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 v2 0/1] Bluetooth: ISO: Reassociate a socket with an active BIS
Date: Fri, 17 Nov 2023 16:20:23 +0000 [thread overview]
Message-ID: <170023802377.26338.10849324218724553463.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231113153800.3771-1-iulia.tanasescu@nxp.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 13 Nov 2023 17:37:59 +0200 you wrote:
> This patch implements a kernel improvement, to be able to reopen a BIS
> socket from userspace and reassociate it with an active BIS connection.
>
> This is useful for a Broadcast Source with multiple BISes - since a BIS
> cannot be terminated independently from other BISes in the BIG, all BIS
> hcons should be linked and kept alive as long as the BIG is active.
>
> [...]
Here is the summary with links:
- [v2,1/1] Bluetooth: ISO: Reassociate a socket with an active BIS
https://git.kernel.org/bluetooth/bluetooth-next/c/498de6c85fe0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-11-17 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 15:37 [PATCH v2 0/1] Bluetooth: ISO: Reassociate a socket with an active BIS Iulia Tanasescu
2023-11-13 15:38 ` [PATCH v2 1/1] " Iulia Tanasescu
2023-11-13 16:40 ` bluez.test.bot
2023-11-17 16:20 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 15:30 [PATCH v2 0/1] " Iulia Tanasescu
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=170023802377.26338.10849324218724553463.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox