From: patchwork-bot+bluetooth@kernel.org
To: Kirill Samburskiy <k.samburskiy@omp.ru>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 0/4] test-vcp: Fix test failing in some environments
Date: Fri, 20 Jun 2025 15:10:06 +0000 [thread overview]
Message-ID: <175043220650.1606561.16885498494907013375.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250620135146.243585-1-k.samburskiy@omp.ru>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 20 Jun 2025 16:51:42 +0300 you wrote:
> This patch fixes test-vcp failing on some environments. It is done by
> shutting down tester IO before test teardown and registering detach
> callbacks to ensure proper cleanup. Similar changes are introduced to
> test-micp to avoid similar problems in the future.
>
> ---
> Note: this is the second version of the patch, the original discussion
> can be found at:
> https://lore.kernel.org/all/20250619153120.126315-1-k.samburskiy@omp.ru
> See patch changelog below for changes in the new version.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/4] shared/bap: ignore NULL attach/detach callbacks
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=71b5ea9bf373
- [BlueZ,v2,2/4] test-vcp: remove unnecessary bt_vcp allocation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f5a4e95d73fe
- [BlueZ,v2,3/4] test-micp: remove unnecessary bt_micp allocation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=659fc8fa7037
- [BlueZ,v2,4/4] shared/tester: shutdown tester IO before test teardown
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a209d69767db
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:[~2025-06-20 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 13:51 [PATCH BlueZ v2 0/4] test-vcp: Fix test failing in some environments Kirill Samburskiy
2025-06-20 13:51 ` [PATCH BlueZ v2 1/4] shared/bap: ignore NULL attach/detach callbacks Kirill Samburskiy
2025-06-20 15:12 ` test-vcp: Fix test failing in some environments bluez.test.bot
2025-06-20 13:51 ` [PATCH BlueZ v2 2/4] test-vcp: remove unnecessary bt_vcp allocation Kirill Samburskiy
2025-06-20 13:51 ` [PATCH BlueZ v2 3/4] test-micp: remove unnecessary bt_micp allocation Kirill Samburskiy
2025-06-20 13:51 ` [PATCH BlueZ v2 4/4] shared/tester: shutdown tester IO before test teardown Kirill Samburskiy
2025-06-20 15:10 ` 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=175043220650.1606561.16885498494907013375.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=k.samburskiy@omp.ru \
--cc=linux-bluetooth@vger.kernel.org \
/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.