From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v2] Bluetooth: btintel: load unlocker.sfi to allow unsigned firmware
Date: Mon, 28 Sep 2026 23:59:07 -0700 (PDT) [thread overview]
Message-ID: <6abb61bb.c21e2895.11c874.9a68@mx.google.com> (raw)
In-Reply-To: <20260929021056.1396791-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1301 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/1175689/
---Test result---
Test Summary:
CheckPatch PASS 0.86 seconds
VerifyFixes PASS 0.10 seconds
VerifySignedoff PASS 0.10 seconds
GitLint FAIL 0.28 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 29.10 seconds
CheckAllWarning PASS 33.15 seconds
CheckSparse PASS 35.38 seconds
BuildKernel32 PASS 29.08 seconds
CheckKernelLLVM PASS 36.56 seconds
TestRunnerSetup PASS 715.39 seconds
IncrementalBuild PASS 26.55 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v2] Bluetooth: btintel: load unlocker.sfi to allow unsigned firmware
35: B1 Line exceeds max length (82>80): "[ 414.150089] Bluetooth: hci0: Firmware timestamp 2026.39 buildtype 3 build 86921"
https://github.com/bluez/bluetooth-next/pull/835
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-29 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 2:10 [PATCH v2] Bluetooth: btintel: load unlocker.sfi to allow unsigned firmware Kiran K
2026-09-29 6:59 ` bluez.test.bot [this message]
2026-09-29 15:04 ` Luiz Augusto von Dentz
2026-09-29 16:13 ` K, Kiran
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=6abb61bb.c21e2895.11c874.9a68@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