All of lore.kernel.org
 help / color / mirror / Atom feed
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/1] iso-tester: Add test for bcast AC 13 reconnect
Date: Mon, 20 Nov 2023 14:50:24 +0000	[thread overview]
Message-ID: <170049182489.24101.6153640383647595323.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231113153942.3875-1-iulia.tanasescu@nxp.com>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon, 13 Nov 2023 17:39:41 +0200 you wrote:
> This adds a test for the Broadcast AC 13 reconnect scenario: 2 BIS
> sockets are connected, one of them is closed and then reopened, and
> it is reassociated with the free BIS hcon inside the kernel space.
> 
> This depends on the kernel support added by patch
> Bluetooth: ISO: Reassociate a socket with an active BIS.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/1] iso-tester: Add test for bcast AC 13 reconnect
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=58e6ef54e672

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2023-11-20 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 15:39 [PATCH BlueZ 0/1] iso-tester: Add test for bcast AC 13 reconnect Iulia Tanasescu
2023-11-13 15:39 ` [PATCH BlueZ 1/1] " Iulia Tanasescu
2023-11-13 17:04   ` bluez.test.bot
2023-11-20 14:50 ` patchwork-bot+bluetooth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-01 15:31 [PATCH BlueZ 0/1] " Iulia Tanasescu
2023-10-30 15:49 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=170049182489.24101.6153640383647595323.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.