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 Mezz reworked for BT over UART
Date: Thu, 23 Jul 2026 08:46:37 -0700 (PDT) [thread overview]
Message-ID: <6a62375d.6f91ca5b.c0d5c.9a1f@mx.google.com> (raw)
In-Reply-To: <20260723-rb3-industrial-bt-uart-v1-1-3c8e580c09d1@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 4766 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=1133207
---Test result---
Test Summary:
CheckPatch FAIL 3.78 seconds
VerifyFixes PASS 0.14 seconds
VerifySignedoff PASS 0.14 seconds
GitLint PASS 1.01 seconds
SubjectPrefix FAIL 0.46 seconds
BuildKernel PASS 27.03 seconds
CheckAllWarning PASS 30.93 seconds
CheckSparse PASS 28.48 seconds
BuildKernel32 PASS 26.47 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 505.18 seconds
TestRunner_l2cap-tester PASS 63.01 seconds
TestRunner_iso-tester PASS 86.12 seconds
TestRunner_bnep-tester PASS 19.37 seconds
TestRunner_mgmt-tester FAIL 222.76 seconds
TestRunner_rfcomm-tester PASS 25.78 seconds
TestRunner_sco-tester PASS 35.00 seconds
TestRunner_ioctl-tester PASS 26.77 seconds
TestRunner_mesh-tester FAIL 26.97 seconds
TestRunner_smp-tester PASS 23.95 seconds
TestRunner_userchan-tester PASS 20.89 seconds
TestRunner_6lowpan-tester PASS 24.22 seconds
IncrementalBuild PASS 28.40 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/3] Bluetooth: qca: add QCC2072 support
WARNING: DT compatible string "qcom,qcc2072-bt" appears un-documented -- check ./Documentation/devicetree/bindings/
#457: FILE: drivers/bluetooth/hci_qca.c:2811:
+ { .compatible = "qcom,qcc2072-bt", .data = &qca_soc_data_qcc2072},
total: 0 errors, 1 warnings, 240 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/14706139.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.
[2/3] arm64: dts: qcom: kodiak: mark PCIe root port as bridge
WARNING: DT compatible string vendor "pciclass" appears un-documented -- check ./Documentation/devicetree/bindings/vendor-prefixes.yaml
#188: FILE: arch/arm64/boot/dts/qcom/kodiak.dtsi:2299:
+ compatible = "pciclass,0604";
total: 0 errors, 1 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/14706140.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.
[3/3] arm64: dts: qcom: rb3gen2: add Industrial BT UART overlay
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#203:
new file mode 100644
total: 0 errors, 1 warnings, 143 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/14706141.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
##############################
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: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.256 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 2.435 seconds
Mesh - Send cancel - 2 Timed out 1.985 seconds
https://github.com/bluez/bluetooth-next/pull/482
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-23 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260723-rb3-industrial-bt-uart-v1-0-3c8e580c09d1@oss.qualcomm.com>
[not found] ` <20260723-rb3-industrial-bt-uart-v1-2-3c8e580c09d1@oss.qualcomm.com>
2026-07-23 19:07 ` [PATCH 2/3] arm64: dts: qcom: kodiak: mark PCIe root port as bridge Dmitry Baryshkov
2026-07-23 19:31 ` Krzysztof Kozlowski
[not found] ` <20260723-rb3-industrial-bt-uart-v1-3-3c8e580c09d1@oss.qualcomm.com>
2026-07-23 19:10 ` [PATCH 3/3] arm64: dts: qcom: rb3gen2: add Industrial BT UART overlay Dmitry Baryshkov
[not found] ` <20260723-rb3-industrial-bt-uart-v1-1-3c8e580c09d1@oss.qualcomm.com>
2026-07-23 15:46 ` bluez.test.bot [this message]
2026-07-23 19:06 ` [PATCH 1/3] Bluetooth: qca: add QCC2072 support Dmitry Baryshkov
2026-07-23 19:26 ` Krzysztof Kozlowski
2026-07-23 19:19 ` Krzysztof Kozlowski
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=6a62375d.6f91ca5b.c0d5c.9a1f@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