From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, rahul.samana@oss.qualcomm.com
Subject: RE: Bluetooth: qca: enable QCC2072 on RB3 Gen 2 Industrial
Date: Fri, 07 Aug 2026 15:10:28 -0700 (PDT) [thread overview]
Message-ID: <6a7657d4.7d702ed2.13dab5.cc5d@mx.google.com> (raw)
In-Reply-To: <20260727-rb3-industrial-bt-uart-v2-1-2d100f30e202@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 4906 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=1135254
---Test result---
Test Summary:
CheckPatch FAIL 4.30 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.09 seconds
GitLint PASS 1.32 seconds
SubjectPrefix FAIL 0.48 seconds
BuildKernel PASS 22.62 seconds
CheckAllWarning PASS 26.56 seconds
CheckSparse PASS 26.14 seconds
BuildKernel32 PASS 24.61 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 412.88 seconds
TestRunner_l2cap-tester PASS 61.08 seconds
TestRunner_iso-tester PASS 89.26 seconds
TestRunner_bnep-tester PASS 17.04 seconds
TestRunner_mgmt-tester FAIL 210.66 seconds
TestRunner_rfcomm-tester PASS 23.54 seconds
TestRunner_sco-tester PASS 33.66 seconds
TestRunner_ioctl-tester PASS 24.51 seconds
TestRunner_mesh-tester FAIL 23.82 seconds
TestRunner_smp-tester PASS 21.68 seconds
TestRunner_userchan-tester PASS 18.12 seconds
TestRunner_6lowpan-tester PASS 20.91 seconds
IncrementalBuild PASS 30.06 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2,1/6] dt-bindings: bluetooth: qca: add QCC2072
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#192:
new file mode 100644
total: 0 errors, 1 warnings, 39 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14713184.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
[v2,5/6] arm64: dts: qcom: kodiak: mark PCIe root port as bridge
WARNING: Duplicate signature
#182:
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
WARNING: DT compatible string vendor "pciclass" appears un-documented -- check ./Documentation/devicetree/bindings/vendor-prefixes.yaml
#195: FILE: arch/arm64/boot/dts/qcom/kodiak.dtsi:2299:
+ compatible = "pciclass,0604";
total: 0 errors, 2 warnings, 7 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14713188.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
[v2,6/6] arm64: dts: qcom: rb3gen2: add Industrial BT UART overlay
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#206:
new file mode 100644
total: 0 errors, 1 warnings, 139 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14713189.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 501, Passed: 496 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.237 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 1.868 seconds
Mesh - Send cancel - 2 Timed out 1.992 seconds
https://github.com/bluez/bluetooth-next/pull/553
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-07 22:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 15:45 [PATCH v2 0/6] Bluetooth: qca: enable QCC2072 on RB3 Gen 2 Industrial Rahul Samana
2026-07-27 15:45 ` [PATCH v2 1/6] dt-bindings: bluetooth: qca: add QCC2072 Rahul Samana
2026-07-27 16:32 ` Bluetooth: qca: enable QCC2072 on RB3 Gen 2 Industrial bluez.test.bot
2026-07-31 9:46 ` [PATCH v2 1/6] dt-bindings: bluetooth: qca: add QCC2072 Krzysztof Kozlowski
2026-07-31 14:45 ` Rahul Samana
2026-07-31 15:04 ` Krzysztof Kozlowski
2026-07-31 15:51 ` Rahul Samana
2026-08-01 14:48 ` Krzysztof Kozlowski
2026-08-01 15:31 ` Rahul Samana
2026-08-01 15:49 ` Krzysztof Kozlowski
2026-08-05 12:09 ` Manivannan Sadhasivam
2026-08-05 12:33 ` Krzysztof Kozlowski
2026-08-05 14:12 ` Manivannan Sadhasivam
2026-08-05 14:36 ` Krzysztof Kozlowski
2026-08-05 14:52 ` Manivannan Sadhasivam
2026-08-07 9:40 ` Dmitry Baryshkov
2026-08-10 10:28 ` Krzysztof Kozlowski
2026-08-07 9:57 ` Dmitry Baryshkov
2026-08-10 10:27 ` Krzysztof Kozlowski
2026-08-07 22:10 ` bluez.test.bot [this message]
2026-07-27 15:45 ` [PATCH v2 2/6] Bluetooth: qca: add QCC2072 support Rahul Samana
2026-07-31 15:09 ` Dmitry Baryshkov
2026-07-31 17:51 ` Rahul Samana
2026-07-27 15:45 ` [PATCH v2 3/6] power: sequencing: pwrseq-pcie-m2: add QCC2072 Rahul Samana
2026-07-27 15:45 ` [PATCH v2 4/6] arm64: dts: qcom: qcs6490-rb3gen2: label BT PMU and M.2 PCI node Rahul Samana
2026-07-31 15:30 ` Rahul Samana
2026-07-27 15:45 ` [PATCH v2 5/6] arm64: dts: qcom: kodiak: mark PCIe root port as bridge Rahul Samana
2026-07-27 15:57 ` Rahul Samana
2026-07-29 12:29 ` Konrad Dybcio
2026-07-27 15:45 ` [PATCH v2 6/6] arm64: dts: qcom: rb3gen2: add Industrial BT UART overlay Rahul Samana
2026-07-29 12:31 ` Konrad Dybcio
2026-07-31 6:53 ` Rahul Samana
2026-07-31 12:50 ` Konrad Dybcio
2026-07-31 14:48 ` Rahul Samana
2026-07-31 15:49 ` Konrad Dybcio
2026-07-31 17:50 ` Rahul Samana
2026-08-02 3:38 ` Bjorn Andersson
2026-08-05 6:18 ` Rahul Samana
2026-08-06 23:02 ` Bjorn Andersson
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=6a7657d4.7d702ed2.13dab5.cc5d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=rahul.samana@oss.qualcomm.com \
/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;
as well as URLs for NNTP newsgroup(s).