From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] tester.config: add missing CRYPTO_AES
Date: Thu, 21 May 2026 13:30:07 +0000 [thread overview]
Message-ID: <177937020756.309926.1774626011773589967.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <478a4d370bc0b20b98223507166dfd580ae8477d.1779051031.git.pav@iki.fi>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 17 May 2026 23:51:30 +0300 you wrote:
> Kernel commit 4a1507625b0 ("Bluetooth: SMP: Use AES-CMAC library
> API") removed CRYPTO_AES from the default Bluetooth kernel config.
>
> This causes Bluetooth testbots to fail silently with "Not Run" status:
>
> Basic Framework - Success - init
> Read Index List callback
> Status: 0x00
> Bluetooth: hci0: Opcode 0x0c03 failed: -110
> Bluetooth: hci0: Opcode 0x0c03 failed: -110
> hciemu: Failed to open vhci
> Failed to setup HCI emulation
> Basic Framework - Success - pre setup failed
> Basic Framework - Success - done
> ...
> SCO CVSD Listen Send - Success Not Run
> Total: 30, Passed: 0 (0.0%), Failed: 0, Not Run: 30
>
> [...]
Here is the summary with links:
- [BlueZ] tester.config: add missing CRYPTO_AES
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2470448ed9d7
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:[~2026-05-21 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 20:51 [PATCH BlueZ] tester.config: add missing CRYPTO_AES Pauli Virtanen
2026-05-17 22:05 ` [BlueZ] " bluez.test.bot
2026-05-21 13:30 ` 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=177937020756.309926.1774626011773589967.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox