From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ PATCH v8 1/8] lib: Add definitions for ISO socket
Date: Fri, 22 Jul 2022 20:40:17 +0000 [thread overview]
Message-ID: <165852241713.788.6962201186413090937.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220630221452.638591-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 30 Jun 2022 15:14:45 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> ---
> v2: Fix CI findings.
> v3: Add patch fixing mgmt-tester Read EXP Features tests.
> v4: Rebase and add flag EXP_FEAT_ISO_SOCKET
> v5: Add BT_DEFER_SETUP tests to iso-tester
> v6: Make iso-tester disable ISO Socket experimental UUID after each test
> v7: Fix scan-build findings
> v8: Add tests Defer and Defer send which use DEFER_SETUP when connecting which
> emulates the QoS state of BAP where a SetCIGParameter shall be used without
> CreateCIS which is left to just Enabling state.
>
> [...]
Here is the summary with links:
- [BlueZ,v8,1/8] lib: Add definitions for ISO socket
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b031e4dc8c4e
- [BlueZ,v8,2/8] shared/util: Decode BlueZ Experimental ISO Socket UUID
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=cc482ad3780b
- [BlueZ,v8,3/8] mgmt-tester: Fix Read Exp Feature tests
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=9c65bad7a878
- [BlueZ,v8,4/8] adapter: Add support for setting ISO Socket experimental feature
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8dc5b5e1ba6b
- [BlueZ,v8,5/8] btio: Add support for ISO sockets
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b1b575cf1720
- [BlueZ,v8,6/8] tools: Add iso-tester
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=26ee34d7be40
- [BlueZ,v8,7/8] tools: Add isotest tool
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=037ed8c5b12a
- [BlueZ,v8,8/8] isotest: Add documentation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4314f7066721
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:[~2022-07-22 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 22:14 [BlueZ PATCH v8 1/8] lib: Add definitions for ISO socket Luiz Augusto von Dentz
2022-06-30 22:14 ` [BlueZ PATCH v8 2/8] shared/util: Decode BlueZ Experimental ISO Socket UUID Luiz Augusto von Dentz
2022-06-30 22:14 ` [BlueZ PATCH v8 3/8] mgmt-tester: Fix Read Exp Feature tests Luiz Augusto von Dentz
2022-06-30 22:14 ` [BlueZ PATCH v8 4/8] adapter: Add support for setting ISO Socket experimental feature Luiz Augusto von Dentz
2022-06-30 22:14 ` [BlueZ PATCH v8 5/8] btio: Add support for ISO sockets Luiz Augusto von Dentz
2022-06-30 22:14 ` [BlueZ PATCH v8 6/8] tools: Add iso-tester Luiz Augusto von Dentz
2022-06-30 22:14 ` [BlueZ PATCH v8 7/8] tools: Add isotest tool Luiz Augusto von Dentz
2022-06-30 22:14 ` [BlueZ PATCH v8 8/8] isotest: Add documentation Luiz Augusto von Dentz
2022-07-01 2:28 ` [BlueZ,v8,1/8] lib: Add definitions for ISO socket bluez.test.bot
2022-07-22 20: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=165852241713.788.6962201186413090937.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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