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=806363 ---Test result--- Test Summary: CheckPatch FAIL 2.51 seconds GitLint FAIL 1.18 seconds SubjectPrefix FAIL 0.57 seconds BuildKernel PASS 28.39 seconds CheckAllWarning PASS 30.04 seconds CheckSparse PASS 35.78 seconds CheckSmatch PASS 99.11 seconds BuildKernel32 PASS 26.63 seconds TestRunnerSetup PASS 415.33 seconds TestRunner_l2cap-tester PASS 23.06 seconds TestRunner_iso-tester PASS 46.68 seconds TestRunner_bnep-tester PASS 10.39 seconds TestRunner_mgmt-tester PASS 174.49 seconds TestRunner_rfcomm-tester PASS 10.92 seconds TestRunner_sco-tester PASS 14.36 seconds TestRunner_ioctl-tester PASS 12.19 seconds TestRunner_mesh-tester PASS 8.83 seconds TestRunner_smp-tester PASS 9.83 seconds TestRunner_userchan-tester PASS 7.44 seconds IncrementalBuild PASS 36.18 seconds Details ############################## Test: CheckPatch - FAIL Desc: Run checkpatch.pl script Output: [v2,01/35] lib/find: add atomic find_bit() primitives WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #269: FILE: include/linux/find.h:35: +unsigned long _find_and_set_bit(volatile unsigned long *addr, unsigned long nbits); WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #270: FILE: include/linux/find.h:36: +unsigned long _find_and_set_next_bit(volatile unsigned long *addr, unsigned long nbits, WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #272: FILE: include/linux/find.h:38: +unsigned long _find_and_set_bit_lock(volatile unsigned long *addr, unsigned long nbits); WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #273: FILE: include/linux/find.h:39: +unsigned long _find_and_set_next_bit_lock(volatile unsigned long *addr, unsigned long nbits, WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #275: FILE: include/linux/find.h:41: +unsigned long _find_and_clear_bit(volatile unsigned long *addr, unsigned long nbits); WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #276: FILE: include/linux/find.h:42: +unsigned long _find_and_clear_next_bit(volatile unsigned long *addr, unsigned long nbits, WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #303: FILE: include/linux/find.h:490: +unsigned long find_and_set_bit(volatile unsigned long *addr, unsigned long nbits) WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #340: FILE: include/linux/find.h:527: +unsigned long find_and_set_next_bit(volatile unsigned long *addr, WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #369: FILE: include/linux/find.h:556: +unsigned long find_and_set_bit_wrap(volatile unsigned long *addr, WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #398: FILE: include/linux/find.h:585: +unsigned long find_and_set_bit_lock(volatile unsigned long *addr, unsigned long nbits) WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #434: FILE: include/linux/find.h:621: +unsigned long find_and_set_next_bit_lock(volatile unsigned long *addr, WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #464: FILE: include/linux/find.h:651: +unsigned long find_and_set_bit_wrap_lock(volatile unsigned long *addr, WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #492: FILE: include/linux/find.h:679: +static inline unsigned long find_and_clear_bit(volatile unsigned long *addr, unsigned long nbits) WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #528: FILE: include/linux/find.h:715: +unsigned long find_and_clear_next_bit(volatile unsigned long *addr, WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #587: FILE: lib/find_bit.c:119: +unsigned long _find_and_set_bit(volatile unsigned long *addr, unsigned long nbits) WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #601: FILE: lib/find_bit.c:133: +unsigned long _find_and_set_next_bit(volatile unsigned long *addr, WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #616: FILE: lib/find_bit.c:148: +unsigned long _find_and_set_bit_lock(volatile unsigned long *addr, unsigned long nbits) WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #630: FILE: lib/find_bit.c:162: +unsigned long _find_and_set_next_bit_lock(volatile unsigned long *addr, WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #645: FILE: lib/find_bit.c:177: +unsigned long _find_and_clear_bit(volatile unsigned long *addr, unsigned long nbits) WARNING: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst #659: FILE: lib/find_bit.c:191: +unsigned long _find_and_clear_next_bit(volatile unsigned long *addr, total: 0 errors, 20 warnings, 402 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/src/13477429.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: [v2,01/35] lib/find: add atomic find_bit() primitives 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 8: B3 Line contains hard tab characters (\t): " for (idx = 0; idx < nbits; idx++)" 9: B3 Line contains hard tab characters (\t): " if (test_and_clear_bit(idx, bitmap))" 10: B3 Line contains hard tab characters (\t): " do_something(idx);" 14: B3 Line contains hard tab characters (\t): " do {" 15: B3 Line contains hard tab characters (\t): " bit = find_first_bit(bitmap, nbits);" 16: B3 Line contains hard tab characters (\t): " if (bit >= nbits)" 17: B3 Line contains hard tab characters (\t): " return nbits;" 18: B3 Line contains hard tab characters (\t): " } while (!test_and_clear_bit(bit, bitmap));" 19: B3 Line contains hard tab characters (\t): " return bit;" 24: B3 Line contains hard tab characters (\t): " for_each_test_and_clear_bit(idx, bitmap, nbits)" 25: B3 Line contains hard tab characters (\t): " do_something(idx);" 28: B3 Line contains hard tab characters (\t): " return find_and_clear_bit(bitmap, nbits);" 69: B3 Line contains hard tab characters (\t): " find_and_set_bit(addr, nbits);" 70: B3 Line contains hard tab characters (\t): " find_and_set_next_bit(addr, nbits, start);" 71: B3 Line contains hard tab characters (\t): " ..." ############################## 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 --- Regards, Linux Bluetooth
