From: patchwork-bot+bluetooth@kernel.org
To: Max Chou <max.chou@realtek.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
pmenzel@molgen.mpg.de, hildawu@realtek.com,
alex_lu@realsil.com.cn, niall_ni@realsil.com.cn,
kidman@realtek.com
Subject: Re: [PATCH v2] Bluetooth: btrtl: Avoid loading the config file on security chips
Date: Mon, 10 Nov 2025 20:40:05 +0000 [thread overview]
Message-ID: <176280720577.2767842.12707890897825880564.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251105120204.458231-1-max.chou@realtek.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 5 Nov 2025 20:02:04 +0800 you wrote:
> For chips with security enabled, it's only possible to load firmware
> with a valid signature pattern.
> If key_id is not zero, it indicates a security chip, and the driver will
> not load the config file.
>
> - Example log for a security chip.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: btrtl: Avoid loading the config file on security chips
https://git.kernel.org/bluetooth/bluetooth-next/c/9063119bdaee
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:[~2025-11-10 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 12:02 [PATCH v2] Bluetooth: btrtl: Avoid loading the config file on security chips Max Chou
2025-11-05 12:51 ` [v2] " bluez.test.bot
2025-11-10 20:40 ` patchwork-bot+bluetooth [this message]
2025-11-11 9:05 ` [PATCH v2] " Paul Menzel
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=176280720577.2767842.12707890897825880564.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alex_lu@realsil.com.cn \
--cc=hildawu@realtek.com \
--cc=kidman@realtek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.com \
--cc=niall_ni@realsil.com.cn \
--cc=pmenzel@molgen.mpg.de \
/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