RE: [BlueZ,v1,1/2] shared/lc3: Add QoS definitions

[bluez.test.bot@gmail.com]

[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.51 seconds
GitLint                       PASS      0.39 seconds
BuildEll                      PASS      24.94 seconds
BluezMake                     PASS      664.19 seconds
MakeCheck                     PASS      11.78 seconds
MakeDistcheck                 PASS      154.38 seconds
CheckValgrind                 PASS      216.26 seconds
CheckSmatch                   PASS      319.98 seconds
bluezmakeextell               PASS      100.07 seconds
IncrementalBuild              PASS      1131.18 seconds
ScanBuild                     PASS      907.53 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v1,2/2] test-bap: Introduce QoS tests for LC3
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#78: 
  Verify that a Unicast Client IUT can initiate a Config QoS operation for the

/github/workspace/src/src/13474875.patch total: 0 errors, 1 warnings, 992 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/13474875.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.




---
Regards,
Linux Bluetooth