From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/5] iso-tester: always use DEFER_SETUP for multiple CIS in same CIG
Date: Mon, 22 May 2023 20:20:20 +0000 [thread overview]
Message-ID: <168478682055.7079.605631444073463509.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <024df2d86c14fc811701ba27bfa576476bc9c0d6.1684682575.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 21 May 2023 15:27:34 +0000 you wrote:
> There is a race between multiple connect() for CIS in the same CIG.
> connect() will both reconfigure the CIG and connect the CIS, but CIG
> cannot be reconfigured once one CIS has already connected. That these
> tests pass currently relies on some timing/event ordering in the
> emulator.
>
> Connecting multiple CIS in same CIG is meant to be done using
> DEFER_SETUP, so change the tests to use it, so we test the intended
> usage.
>
> [...]
Here is the summary with links:
- [BlueZ,1/5] iso-tester: always use DEFER_SETUP for multiple CIS in same CIG
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a88c74e29b6e
- [BlueZ,2/5] shared/tester: retain test failure status
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=195b9abbae0e
- [BlueZ,3/5] btdev: support multiple CIG
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=678265f37c28
- [BlueZ,4/5] btdev: report right reason for local Disconnect complete
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0c32cfdf9462
- [BlueZ,5/5] iso-tester: add tests for multiple simultaneous CIG
(no matching commit)
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-05-22 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 15:27 [PATCH BlueZ 1/5] iso-tester: always use DEFER_SETUP for multiple CIS in same CIG Pauli Virtanen
2023-05-21 15:27 ` [PATCH BlueZ 2/5] shared/tester: retain test failure status Pauli Virtanen
2023-05-21 15:27 ` [PATCH BlueZ 3/5] btdev: support multiple CIG Pauli Virtanen
2023-05-21 15:27 ` [PATCH BlueZ 4/5] btdev: report right reason for local Disconnect complete Pauli Virtanen
2023-05-21 15:27 ` [PATCH BlueZ 5/5] iso-tester: add tests for multiple simultaneous CIG Pauli Virtanen
2023-05-22 18:28 ` Luiz Augusto von Dentz
2023-05-22 20:38 ` Pauli Virtanen
2023-05-22 20:48 ` Luiz Augusto von Dentz
2023-05-22 23:08 ` Luiz Augusto von Dentz
2023-05-21 16:15 ` hci_sync req_complete_skb does not get called? Pauli Virtanen
2023-05-21 16:37 ` bluez.test.bot
2023-05-21 18:11 ` [BlueZ,1/5] iso-tester: always use DEFER_SETUP for multiple CIS in same CIG bluez.test.bot
2023-05-22 20:20 ` patchwork-bot+bluetooth [this message]
2023-05-22 20:27 ` [PATCH BlueZ 1/5] " Luiz Augusto von Dentz
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=168478682055.7079.605631444073463509.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.