From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v1] Bluetooth: btintel: load unlocker.sfi to allow unsigned firmware
Date: Wed, 23 Sep 2026 03:59:02 -0700 (PDT) [thread overview]
Message-ID: <6ab3b0f6.6b931ad5.20b80.70df@mx.google.com> (raw)
In-Reply-To: <20260923102427.1147212-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/series/1172102/
---Test result---
Test Summary:
CheckPatch PASS 1.04 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.12 seconds
GitLint FAIL 0.34 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 29.80 seconds
CheckAllWarning PASS 32.51 seconds
CheckSparse PASS 35.17 seconds
BuildKernel32 PASS 28.68 seconds
CheckKernelLLVM PASS 34.91 seconds
TestRunnerSetup PASS 744.85 seconds
IncrementalBuild PASS 27.50 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v1] Bluetooth: btintel: load unlocker.sfi to allow unsigned firmware
32: B1 Line exceeds max length (82>80): "[ 414.150089] Bluetooth: hci0: Firmware timestamp 2026.39 buildtype 3 build 86921"
38: B1 Line exceeds max length (99>80): "[ 414.150739] Bluetooth: hci0: Waiting for post-FW-download coredump to complete (timeout 5000 ms)"
39: B1 Line exceeds max length (83>80): "[ 414.150744] Bluetooth: hci0: Skipping coredump: debug traces routed to WiFi DBGC"
https://github.com/bluez/bluetooth-next/pull/813
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-09-23 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 10:24 [PATCH v1] Bluetooth: btintel: load unlocker.sfi to allow unsigned firmware Kiran K
2026-09-23 10:59 ` bluez.test.bot [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=6ab3b0f6.6b931ad5.20b80.70df@mx.google.com \
--to=bluez.test.bot@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox