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=1119976 ---Test result--- Test Summary: CheckPatch FAIL 7.97 seconds VerifyFixes PASS 0.13 seconds VerifySignedoff PASS 0.13 seconds GitLint FAIL 2.89 seconds SubjectPrefix FAIL 1.10 seconds BuildKernel PASS 27.20 seconds CheckAllWarning PASS 29.59 seconds CheckSparse PASS 29.34 seconds BuildKernel32 PASS 26.43 seconds CheckKernelLLVM SKIP 0.00 seconds TestRunnerSetup PASS 498.54 seconds TestRunner_l2cap-tester PASS 58.96 seconds TestRunner_iso-tester PASS 87.85 seconds TestRunner_bnep-tester PASS 18.80 seconds TestRunner_mgmt-tester FAIL 208.06 seconds TestRunner_rfcomm-tester PASS 26.03 seconds TestRunner_sco-tester PASS 32.36 seconds TestRunner_ioctl-tester PASS 25.47 seconds TestRunner_mesh-tester FAIL 25.88 seconds TestRunner_smp-tester PASS 23.24 seconds TestRunner_userchan-tester PASS 19.55 seconds TestRunner_6lowpan-tester PASS 22.78 seconds IncrementalBuild PASS 75.39 seconds Details ############################## Test: CheckPatch - FAIL Desc: Run checkpatch.pl script Output: [v7,5/9] block: implement NVMEM provider WARNING: please write a help paragraph that fully describes the config symbol with at least 4 lines #213: FILE: block/Kconfig:212: +config BLK_NVMEM + bool "Block device NVMEM provider" + depends on OF + depends on NVMEM + help + Allow block devices (or partitions) to act as NVMEM providers, + typically used with eMMC to store MAC addresses or Wi-Fi + calibration data on embedded devices. + WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #235: new file mode 100644 total: 0 errors, 2 warnings, 172 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/14657089.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: [v7,9/9] arm64: dts: qcom: arduino-imola: Describe NVMEM layout for WiFi/BT addresses 1: T1 Title exceeds max length (85>80): "[v7,9/9] arm64: dts: qcom: arduino-imola: Describe NVMEM layout for WiFi/BT addresses" ############################## 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 "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.233 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.529 seconds Mesh - Send cancel - 2 Timed out 1.985 seconds https://github.com/bluez/bluetooth-next/pull/382 --- Regards, Linux Bluetooth