All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yauhen.kharuzhy@softeq.com
Subject: RE: [BlueZ,v2,1/2] shared/mcp: Implement next/previous track commands
Date: Wed, 19 Jun 2024 07:23:19 -0700 (PDT)	[thread overview]
Message-ID: <6672e9d7.050a0220.f618d.9323@mx.google.com> (raw)
In-Reply-To: <20240619120433.3666313-1-yauhen.kharuzhy@softeq.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.15 seconds
GitLint                       PASS      0.80 seconds
BuildEll                      PASS      24.92 seconds
BluezMake                     PASS      1708.96 seconds
MakeCheck                     PASS      13.42 seconds
MakeDistcheck                 PASS      181.15 seconds
CheckValgrind                 PASS      255.98 seconds
CheckSmatch                   PASS      366.72 seconds
bluezmakeextell               PASS      124.83 seconds
IncrementalBuild              PASS      3141.47 seconds
ScanBuild                     PASS      1103.64 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2,2/2] mcp: Implement Next Track and Previous Track commands
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#92: 
Add implementation of Next/Previous Track commands to the audio/mcp profile.

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


      parent reply	other threads:[~2024-06-19 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 12:04 [PATCH BlueZ v2 1/2] shared/mcp: Implement next/previous track commands Yauhen Kharuzhy
2024-06-19 12:04 ` [PATCH BlueZ v2 2/2] mcp: Implement Next Track and Previous Track commands Yauhen Kharuzhy
2024-06-19 14:10 ` [PATCH BlueZ v2 1/2] shared/mcp: Implement next/previous track commands patchwork-bot+bluetooth
2024-06-19 14:23 ` bluez.test.bot [this message]

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=6672e9d7.050a0220.f618d.9323@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=yauhen.kharuzhy@softeq.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.