From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org,
chethan.tumkur.narayan@intel.com,
chandrashekar.devegowda@intel.com
Subject: Re: [PATCH v2] Bluetooth: btintel: check FIPS status before firmware download
Date: Wed, 28 Oct 2026 19:40:05 +0000 [thread overview]
Message-ID: <179321640558.1390808.2098882383641688916.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261027131850.3652839-1-kiran.k@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 27 Oct 2026 18:48:50 +0530 you wrote:
> Intel Bluetooth controllers (PCIe and USB) from Scorpius Peak2 onwards,
> except BlazarIW, report bootloader self-test results (CRC, security,
> and patch) in the INTEL_TLV_FIPS_STS TLV of the Intel Read Version
> event. Act on them before firmware download:
>
> 1. CRC failure -> abort download.
> 2. Security failure -> abort on USB / HW reset and retry on PCIe.
> 3. Patch failure -> abort on USB / HW reset and retry on PCIe.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: btintel: check FIPS status before firmware download
https://git.kernel.org/bluetooth/bluetooth-next/c/1081a6ef8f1e
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-10-28 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 13:18 [PATCH v2] Bluetooth: btintel: check FIPS status before firmware download Kiran K
2026-10-27 16:49 ` [v2] " bluez.test.bot
2026-10-28 19: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=179321640558.1390808.2098882383641688916.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--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.