All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, nitin.jadhav@nxp.com
Subject: RE: Code handling for VOCS service
Date: Wed, 07 Jun 2023 06:37:07 -0700 (PDT)	[thread overview]
Message-ID: <64808803.050a0220.7ca89.088c@mx.google.com> (raw)
In-Reply-To: <20230607121342.6136-2-nitin.jadhav@nxp.com>

[-- Attachment #1: Type: text/plain, Size: 3713 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=754867

---Test result---

Test Summary:
CheckPatch                    FAIL      1.74 seconds
GitLint                       PASS      0.72 seconds
BuildEll                      PASS      27.11 seconds
BluezMake                     PASS      863.57 seconds
MakeCheck                     PASS      12.34 seconds
MakeDistcheck                 PASS      154.02 seconds
CheckValgrind                 PASS      255.60 seconds
CheckSmatch                   PASS      340.33 seconds
bluezmakeextell               PASS      102.67 seconds
IncrementalBuild              PASS      1417.56 seconds
ScanBuild                     WARNING   1055.29 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2,1/2] Added initial code for handling VOCS
WARNING:LONG_LINE: line length of 93 exceeds 80 columns
#596: FILE: src/shared/vcp.c:1268:
+				uint16_t value_handle, const uint8_t *value, uint16_t length,

WARNING:LONG_LINE: line length of 89 exceeds 80 columns
#614: FILE: src/shared/vcp.c:1340:
+				uint8_t att_ecode, const uint8_t *value, uint16_t length,

WARNING:LONG_LINE: line length of 85 exceeds 80 columns
#624: FILE: src/shared/vcp.c:1350:
+		DBG(vcp, "Unable to read Vol Offset State: error 0x%02x", att_ecode);

WARNING:LONG_LINE: line length of 89 exceeds 80 columns
#639: FILE: src/shared/vcp.c:1365:
+				uint8_t att_ecode, const uint8_t *value, uint16_t length,

WARNING:LONG_LINE: line length of 88 exceeds 80 columns
#649: FILE: src/shared/vcp.c:1375:
+		DBG(vcp, "Unable to read VOCS Audio Location: error 0x%02x", att_ecode);

WARNING:LONG_LINE: line length of 89 exceeds 80 columns
#664: FILE: src/shared/vcp.c:1390:
+				uint8_t att_ecode, const uint8_t *value, uint16_t length,

WARNING:LONG_LINE: line length of 85 exceeds 80 columns
#724: FILE: src/shared/vcp.c:1599:
+						     vcp_voffset_state_notify, NULL);

WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#739: FILE: src/shared/vcp.c:1614:
+		vcp_read_value(vcp, value_handle, read_vocs_audio_location, vcp);

WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#742: FILE: src/shared/vcp.c:1617:
+						     vcp_audio_loc_notify, NULL);

WARNING:LONG_LINE: line length of 83 exceeds 80 columns
#769: FILE: src/shared/vcp.c:1644:
+		vcp_read_value(vcp, value_handle, read_vocs_audio_descriptor, vcp);

WARNING:LONG_LINE: line length of 87 exceeds 80 columns
#771: FILE: src/shared/vcp.c:1646:
+						    vcp_audio_descriptor_notify, NULL);

/github/workspace/src/src/13270609.patch total: 0 errors, 11 warnings, 676 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/13270609.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.


##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
src/shared/vcp.c:1272:2: warning: Null pointer passed to 1st parameter expecting 'nonnull'
        memcpy(vocs_audio_loc_n, value, sizeof(uint32_t));
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2023-06-07 13:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 12:13 [PATCH BlueZ v2 0/2] Code handling for VOCS service Nitin Jadhav
2023-06-07 12:13 ` [PATCH BlueZ v2 1/2] Added initial code for handling VOCS Nitin Jadhav
2023-06-07 12:24   ` Paul Menzel
2023-06-07 13:37   ` bluez.test.bot [this message]
2023-06-07 12:13 ` [PATCH BlueZ v2 2/2] Make VOCS (Secondary) as an included service of VCS (Primary) Nitin Jadhav
  -- strict thread matches above, loose matches on Subject: below --
2023-06-12 13:32 [PATCH BlueZ v5 1/3] lib/uuid.h: Add VOCS characteristic uuid(s) Nitin Jadhav
2023-06-12 15:34 ` Code handling for VOCS service bluez.test.bot
2023-06-09  9:42 [PATCH BlueZ v4 1/3] lib/uuid.h: Add VOCS characteristic uuid(s) Nitin Jadhav
2023-06-09 11:33 ` Code handling for VOCS service bluez.test.bot
2023-06-08 12:09 [PATCH BlueZ v3 1/2] Title: Added initial code for handling VOCS Nitin Jadhav
2023-06-08 13:36 ` Code handling for VOCS service bluez.test.bot
2023-06-08 16:30   ` Luiz Augusto von Dentz
2023-06-06 12:08 [PATCH BlueZ v1 1/2] Added initial code for handling VOCS NJNXP
2023-06-06 13:31 ` Code handling for VOCS service bluez.test.bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=64808803.050a0220.7ca89.088c@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=nitin.jadhav@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.