From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, marijn.suijten@somainline.org
Subject: RE: [BlueZ,v2] audio/avrcp: Determine Absolute Volume support from feature category 2
Date: Tue, 19 Oct 2021 02:38:16 -0700 (PDT) [thread overview]
Message-ID: <616e9208.1c69fb81.24e25.d7dd@mx.google.com> (raw)
In-Reply-To: <20211019091648.120910-1-marijn.suijten@somainline.org>
[-- Attachment #1: Type: text/plain, Size: 2364 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=566149
---Test result---
Test Summary:
CheckPatch FAIL 0.71 seconds
GitLint FAIL 0.33 seconds
Prep - Setup ELL PASS 52.40 seconds
Build - Prep PASS 0.23 seconds
Build - Configure PASS 9.09 seconds
Build - Make PASS 218.92 seconds
Make Check PASS 9.54 seconds
Make Distcheck PASS 260.01 seconds
Build w/ext ELL - Configure PASS 9.32 seconds
Build w/ext ELL - Make PASS 203.44 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,v2] audio/avrcp: Determine Absolute Volume support from feature category 2
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#71:
[1]: https://android.googlesource.com/platform/system/bt/+/android-11.0.0_r28/bta/av/bta_av_main.cc#761
/github/workspace/src/12569213.patch total: 0 errors, 1 warnings, 19 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/12569213.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: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[BlueZ,v2] audio/avrcp: Determine Absolute Volume support from feature category 2
1: T1 Title exceeds max length (81>80): "[BlueZ,v2] audio/avrcp: Determine Absolute Volume support from feature category 2"
18: B1 Line exceeds max length (103>80): "[1]: https://android.googlesource.com/platform/system/bt/+/android-11.0.0_r28/bta/av/bta_av_main.cc#761"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-10-19 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 9:16 [PATCH BlueZ v2] audio/avrcp: Determine Absolute Volume support from feature category 2 Marijn Suijten
2021-10-19 9:38 ` bluez.test.bot [this message]
2021-10-19 17:38 ` Luiz Augusto von Dentz
2021-10-25 13:42 ` Marijn Suijten
2021-10-25 17:48 ` Luiz Augusto von Dentz
2021-10-25 18:37 ` Marijn Suijten
2021-10-25 20:32 ` Luiz Augusto von Dentz
2021-10-25 21:02 ` Marijn Suijten
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=616e9208.1c69fb81.24e25.d7dd@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).