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=627939 ---Test result--- Test Summary: CheckPatch FAIL 2.90 seconds GitLint FAIL 2.06 seconds Prep - Setup ELL PASS 42.82 seconds Build - Prep PASS 0.70 seconds Build - Configure PASS 8.63 seconds Build - Make PASS 1251.02 seconds Make Check PASS 11.29 seconds Make Check w/Valgrind PASS 429.57 seconds Make Distcheck PASS 222.48 seconds Build w/ext ELL - Configure PASS 8.50 seconds Build w/ext ELL - Make PASS 1240.28 seconds Incremental Build with patchesPASS 2598.77 seconds Details ############################## Test: CheckPatch - FAIL Desc: Run checkpatch.pl script with rule in .checkpatch.conf Output: [BlueZ,2/2] mgmt-tester: Adds turning on Mesh Experimental feature WARNING:LONG_LINE: line length of 101 exceeds 80 columns #135: FILE: tools/mgmt-tester.c:7358: + tester_warn("Invalid cmd response parameter size %d %d", length, expect_len); /github/workspace/src/12797546.patch total: 0 errors, 1 warnings, 77 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/12797546.patch has style problems, please review. NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO 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 with rule in .gitlint Output: [BlueZ,1/2] docs: Add support for Mesh Scanning and Sending 4: B3 Line contains hard tab characters (\t): " - MESH_RECEIVER - Enable Mesh Receiver with Passive scanning" 5: B3 Line contains hard tab characters (\t): " with a list of AD Types (Mesh and/or Extended Mesh)." 7: B3 Line contains hard tab characters (\t): " - MESH_FEATURES - Requests information on how many simultaneous" 8: B3 Line contains hard tab characters (\t): " outbound mesh packets can be pending at one time." 10: B3 Line contains hard tab characters (\t): " - MESH_TX_PACKET - Send a requested Mesh Packet, perhaps with a" 11: B3 Line contains hard tab characters (\t): " specific fine-timed delay." 13: B3 Line contains hard tab characters (\t): " - MESH_TX_CANCEL - Cancel a prior Mesh TX request that has not" 14: B3 Line contains hard tab characters (\t): " yet completed." 17: B3 Line contains hard tab characters (\t): " - MESH_DEVICE_FOUND - Returned when Mesh is enabled, and one of" 18: B3 Line contains hard tab characters (\t): " the requested AD Types is detected in an incoming" 19: B3 Line contains hard tab characters (\t): " Advertisement." 21: B3 Line contains hard tab characters (\t): " - MESH_TX_COMPLETE - Reports that a prior requested transmission" 22: B3 Line contains hard tab characters (\t): " has completed and no longer consumes one of the available" 23: B3 Line contains hard tab characters (\t): " outbound slots." --- Regards, Linux Bluetooth
