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=1092078 ---Test result--- Test Summary: CheckPatch FAIL 0.77 seconds GitLint FAIL 0.34 seconds SubjectPrefix PASS 0.13 seconds BuildKernel PASS 24.98 seconds CheckAllWarning PASS 27.45 seconds CheckSparse PASS 26.44 seconds BuildKernel32 PASS 24.22 seconds TestRunnerSetup PASS 518.00 seconds TestRunner_rfcomm-tester PASS 63.49 seconds IncrementalBuild PASS 23.77 seconds Details ############################## Test: CheckPatch - FAIL Desc: Run checkpatch.pl script Output: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?) #119: The buggy scenario involves two paths, with each column showing the order within that path: WARNING: The commit message has 'BUG: KASAN: ', perhaps it also needs a 'Fixes:' tag? total: 0 errors, 2 warnings, 0 checks, 65 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/14563150.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: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search 23: B1 Line exceeds max length (91>80): "The buggy scenario involves two paths, with each column showing the order within that path:" https://github.com/bluez/bluetooth-next/pull/160 --- Regards, Linux Bluetooth