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=528479 ---Test result--- Test Summary: CheckPatch PASS 0.52 seconds GitLint FAIL 0.12 seconds BuildKernel FAIL 337.33 seconds TestRunner: Setup PASS 363.65 seconds TestRunner: l2cap-tester PASS 2.59 seconds TestRunner: bnep-tester PASS 1.97 seconds TestRunner: mgmt-tester PASS 30.89 seconds TestRunner: rfcomm-tester PASS 2.18 seconds TestRunner: sco-tester PASS 2.06 seconds TestRunner: smp-tester FAIL 2.18 seconds TestRunner: userchan-tester PASS 2.02 seconds Details ############################## Test: CheckPatch - PASS - 0.52 seconds Run checkpatch.pl script with rule in .checkpatch.conf ############################## Test: GitLint - FAIL - 0.12 seconds Run gitlint with rule in .gitlint Bluetooth: btusb: Remove WAKEUP_DISABLE and add WAKEUP_AUTOSUSPEND for Realtek devices 1: T1 Title exceeds max length (86>72): "Bluetooth: btusb: Remove WAKEUP_DISABLE and add WAKEUP_AUTOSUSPEND for Realtek devices" ############################## Test: BuildKernel - FAIL - 337.33 seconds Build Kernel with minimal configuration supports Bluetooth drivers/bluetooth/btusb.c: In function ‘btusb_prevent_wake’: drivers/bluetooth/btusb.c:3593:15: error: ‘BTUSB_WAKEUP_DISABLE’ undeclared (first use in this function) 3593 | if (test_bit(BTUSB_WAKEUP_DISABLE, &data->flags)) | ^~~~~~~~~~~~~~~~~~~~ drivers/bluetooth/btusb.c:3593:15: note: each undeclared identifier is reported only once for each function it appears in make[2]: *** [scripts/Makefile.build:271: drivers/bluetooth/btusb.o] Error 1 make[1]: *** [scripts/Makefile.build:514: drivers/bluetooth] Error 2 make: *** [Makefile:1841: drivers] Error 2 ############################## Test: TestRunner: Setup - PASS - 363.65 seconds Setup environment for running Test Runner ############################## Test: TestRunner: l2cap-tester - PASS - 2.59 seconds Run test-runner with l2cap-tester Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: bnep-tester - PASS - 1.97 seconds Run test-runner with bnep-tester Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: mgmt-tester - PASS - 30.89 seconds Run test-runner with mgmt-tester Total: 448, Passed: 445 (99.3%), Failed: 0, Not Run: 3 ############################## Test: TestRunner: rfcomm-tester - PASS - 2.18 seconds Run test-runner with rfcomm-tester Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: sco-tester - PASS - 2.06 seconds Run test-runner with sco-tester Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: smp-tester - FAIL - 2.18 seconds Run test-runner with smp-tester Total: 8, Passed: 7 (87.5%), Failed: 1, Not Run: 0 Failed Test Cases SMP Client - SC Request 2 Failed 0.023 seconds ############################## Test: TestRunner: userchan-tester - PASS - 2.02 seconds Run test-runner with userchan-tester Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0 --- Regards, Linux Bluetooth
Attachment:
l2cap-tester.log
Description: Binary data
Attachment:
bnep-tester.log
Description: Binary data
Attachment:
mgmt-tester.log
Description: Binary data
Attachment:
rfcomm-tester.log
Description: Binary data
Attachment:
sco-tester.log
Description: Binary data
Attachment:
smp-tester.log
Description: Binary data
Attachment:
userchan-tester.log
Description: Binary data
