From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v1,1/3] Bluetooth: btintel_pcie: parse FW memory region addresses via mailbox TLV
Date: Tue, 11 Aug 2026 09:09:17 -0700 (PDT) [thread overview]
Message-ID: <6a7b492d.29a6ebfb.30161a.1bee@mx.google.com> (raw)
In-Reply-To: <20260811154553.629211-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1468 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/project/bluetooth/list/?series=1144161
---Test result---
Test Summary:
CheckPatch PASS 3.05 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.12 seconds
GitLint FAIL 1.26 seconds
SubjectPrefix PASS 0.32 seconds
BuildKernel PASS 17.68 seconds
CheckAllWarning PASS 20.39 seconds
CheckSparse PASS 18.45 seconds
BuildKernel32 PASS 16.77 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 310.33 seconds
IncrementalBuild PASS 20.98 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v1,1/3] Bluetooth: btintel_pcie: parse FW memory region addresses via mailbox TLV
1: T1 Title exceeds max length (82>80): "[v1,1/3] Bluetooth: btintel_pcie: parse FW memory region addresses via mailbox TLV"
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/572
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-08-11 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 15:45 [PATCH v1 1/3] Bluetooth: btintel_pcie: parse FW memory region addresses via mailbox TLV Kiran K
2026-08-11 15:45 ` [PATCH v1 2/3] Bluetooth: btintel_pcie: sync mbox tlv parsing with GP0 alive interrupt Kiran K
2026-08-11 15:45 ` [PATCH v1 3/3] Bluetooth: btintel_pcie: Route debug traces to WiFi DBGC by default Kiran K
2026-08-11 16:09 ` 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=6a7b492d.29a6ebfb.30161a.1bee@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 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.