RE: [v3] Bluetooth: btusb: Add support different nvm to distinguish different factory for WCN6855 controller

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=530441

---Test result---

Test Summary:
CheckPatch                    PASS      0.50 seconds
GitLint                       FAIL      0.11 seconds
BuildKernel                   FAIL      413.33 seconds
TestRunner: Setup             PASS      437.73 seconds
TestRunner: l2cap-tester      PASS      3.08 seconds
TestRunner: bnep-tester       PASS      2.14 seconds
TestRunner: mgmt-tester       PASS      34.32 seconds
TestRunner: rfcomm-tester     PASS      2.40 seconds
TestRunner: sco-tester        PASS      2.35 seconds
TestRunner: smp-tester        FAIL      2.41 seconds
TestRunner: userchan-tester   PASS      2.13 seconds

Details
##############################
Test: CheckPatch - PASS - 0.50 seconds
Run checkpatch.pl script with rule in .checkpatch.conf


##############################
Test: GitLint - FAIL - 0.11 seconds
Run gitlint with rule in .gitlint
Bluetooth: btusb: Add support different nvm to distinguish different factory for WCN6855 controller
1: T1 Title exceeds max length (99>72): "Bluetooth: btusb: Add support different nvm to distinguish different factory for WCN6855 controller"


##############################
Test: BuildKernel - FAIL - 413.33 seconds
Build Kernel with minimal configuration supports Bluetooth
drivers/bluetooth/btusb.c: In function ‘btusb_setup_qca_form_nvm_name’:
drivers/bluetooth/btusb.c:3366:1: error: no return statement in function returning non-void [-Werror=return-type]
 3366 | }
      | ^
drivers/bluetooth/btusb.c: In function ‘btusb_setup_qca_load_nvm’:
drivers/bluetooth/btusb.c:3380:34: error: passing argument 1 of ‘btusb_setup_qca_form_nvm_name’ from incompatible pointer type [-Werror=incompatible-pointer-types]
 3380 |    btusb_setup_qca_form_nvm_name(&fwname, sizeof(fwname), ver, "gf");
      |                                  ^~~~~~~
      |                                  |
      |                                  char (*)[64]
drivers/bluetooth/btusb.c:3335:49: note: expected ‘char **’ but argument is of type ‘char (*)[64]’
 3335 | static int btusb_setup_qca_form_nvm_name(char **fwname,
      |                                          ~~~~~~~^~~~~~
drivers/bluetooth/btusb.c:3388:34: error: passing argument 1 of ‘btusb_setup_qca_form_nvm_name’ from incompatible pointer type [-Werror=incompatible-pointer-types]
 3388 |    btusb_setup_qca_form_nvm_name(&fwname, sizeof(fwname), ver, NULL);
      |                                  ^~~~~~~
      |                                  |
      |                                  char (*)[64]
drivers/bluetooth/btusb.c:3335:49: note: expected ‘char **’ but argument is of type ‘char (*)[64]’
 3335 | static int btusb_setup_qca_form_nvm_name(char **fwname,
      |                                          ~~~~~~~^~~~~~
cc1: some warnings being treated as errors
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 - 437.73 seconds
Setup environment for running Test Runner


##############################
Test: TestRunner: l2cap-tester - PASS - 3.08 seconds
Run test-runner with l2cap-tester
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: bnep-tester - PASS - 2.14 seconds
Run test-runner with bnep-tester
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: mgmt-tester - PASS - 34.32 seconds
Run test-runner with mgmt-tester
Total: 448, Passed: 445 (99.3%), Failed: 0, Not Run: 3

##############################
Test: TestRunner: rfcomm-tester - PASS - 2.40 seconds
Run test-runner with rfcomm-tester
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: sco-tester - PASS - 2.35 seconds
Run test-runner with sco-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: smp-tester - FAIL - 2.41 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.024 seconds

##############################
Test: TestRunner: userchan-tester - PASS - 2.13 seconds
Run test-runner with userchan-tester
Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0



---
Regards,
Linux Bluetooth