From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v4,1/2] Bluetooth: btintel: Zero version data before parsing TLVs
Date: Thu, 08 Oct 2026 08:26:55 -0700 (PDT) [thread overview]
Message-ID: <6ac7b63f.33ea1a9e.e076a.cedd@mx.google.com> (raw)
In-Reply-To: <20261008140602.2623464-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1305 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/1181659/
---Test result---
Test Summary:
CheckPatch PASS 1.76 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.12 seconds
GitLint FAIL 0.67 seconds
SubjectPrefix PASS 0.24 seconds
BuildKernel PASS 30.00 seconds
CheckAllWarning PASS 34.53 seconds
CheckSparse PASS 37.04 seconds
BuildKernel32 PASS 29.78 seconds
CheckKernelLLVM PASS 35.80 seconds
TestRunnerSetup PASS 785.35 seconds
IncrementalBuild PASS 31.58 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v4,2/2] 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/888
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-08 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 14:06 [PATCH v4 1/2] Bluetooth: btintel: Zero version data before parsing TLVs Kiran K
2026-10-08 14:06 ` [PATCH v4 2/2] Bluetooth: btintel: load unlocker.sfi to allow unsigned firmware Kiran K
2026-10-08 15:26 ` bluez.test.bot [this message]
2026-10-09 14:00 ` [v4,1/2] Bluetooth: btintel: Zero version data before parsing TLVs Luiz Augusto von Dentz
2026-10-09 19:50 ` [PATCH v4 1/2] " patchwork-bot+bluetooth
2026-10-09 20:00 ` patchwork-bot+bluetooth
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=6ac7b63f.33ea1a9e.e076a.cedd@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