RE: Bluetooth: btusb: Support Qualcomm multi-subsystem QCC2072
From: <hidden>
Date: 2026-09-10 19:01:27
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/1162140/ ---Test result--- Test Summary: CheckPatch FAIL 8.10 seconds VerifyFixes PASS 0.12 seconds VerifySignedoff PASS 0.12 seconds GitLint FAIL 13.19 seconds SubjectPrefix PASS 0.74 seconds BuildKernel PASS 27.98 seconds CheckAllWarning PASS 31.81 seconds CheckSparse PASS 34.97 seconds BuildKernel32 PASS 28.16 seconds CheckKernelLLVM FAIL 27.38 seconds TestRunnerSetup PASS 733.79 seconds TestRunner_l2cap-tester PASS 44.15 seconds TestRunner_iso-tester PASS 114.89 seconds TestRunner_bnep-tester PASS 12.23 seconds TestRunner_mgmt-tester FAIL 149.40 seconds TestRunner_rfcomm-tester PASS 16.84 seconds TestRunner_sco-tester PASS 25.03 seconds TestRunner_ioctl-tester PASS 18.33 seconds TestRunner_mesh-tester FAIL 19.23 seconds TestRunner_smp-tester PASS 15.72 seconds TestRunner_userchan-tester PASS 13.79 seconds TestRunner_6lowpan-tester PASS 16.39 seconds IncrementalBuild PASS 54.67 seconds Details ############################## Test: CheckPatch - FAIL Desc: Run checkpatch.pl script Output: [v4,3/4] Bluetooth: btusb: Build the driver from multiple source files WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #168: drivers/bluetooth/{btusb.c => btusb_main.c} | 0 total: 0 errors, 1 warnings, 11 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/14805662.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. [v4,4/4] Bluetooth: btusb: Add support for Qualcomm multi-subsystem QCC2072 WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #524: new file mode 100644 total: 0 errors, 1 warnings, 4915 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/14805664.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: GitLint - FAIL Desc: Run gitlint Output: [v4,4/4] Bluetooth: btusb: Add support for Qualcomm multi-subsystem QCC2072 8: B3 Line contains hard tab characters (\t): " USB I/F | internal link |" 9: B3 Line contains hard tab characters (\t): "BTHOST -------- |---- PERI -------------- BT |" 10: B3 Line contains hard tab characters (\t): " |_______________________________|" ############################## Test: CheckKernelLLVM - FAIL Desc: Build kernel with LLVM + context analysis Output: drivers/bluetooth/btusb_qcom.c:4255:6: error: mutex 'btusb_qcom_xport_data(hdev).tx_mutex' is not held on every path through here [-Werror,-Wthread-safety-analysis] 4255 | if (is_vendor) | ^ drivers/bluetooth/btusb_qcom.c:4253:3: note: mutex acquired here 4253 | mutex_lock(&xport_data->tx_mutex); | ^ drivers/bluetooth/btusb_qcom.c:4261:3: error: releasing mutex 'btusb_qcom_xport_data(hdev).tx_mutex' that was not held [-Werror,-Wthread-safety-analysis] 4261 | mutex_unlock(&xport_data->tx_mutex); | ^ 2 errors generated. make[4]: *** [scripts/Makefile.build:289: drivers/bluetooth/btusb_qcom.o] Error 1 make[4]: *** Waiting for unfinished jobs.... make[3]: *** [scripts/Makefile.build:549: drivers/bluetooth] Error 2 make[2]: *** [scripts/Makefile.build:549: drivers] Error 2 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [/github/workspace/src/src/Makefile:2187: .] Error 2 make: *** [Makefile:248: __sub-make] Error 2 ############################## 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.148 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.420 seconds Mesh - Send cancel - 2 Timed out 2.000 seconds https://github.com/bluez/bluetooth-next/pull/750 --- Regards, Linux Bluetooth