From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: [BlueZ] tools: avtest: Add reject-code option
Date: Fri, 08 Dec 2023 00:28:48 -0800 (PST) [thread overview]
Message-ID: <6572d3c0.050a0220.77b7b.2b11@mx.google.com> (raw)
In-Reply-To: <20231208070740.611032-1-frederic.danis@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 2360 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=808137
---Test result---
Test Summary:
CheckPatch FAIL 0.71 seconds
GitLint PASS 0.33 seconds
BuildEll PASS 23.97 seconds
BluezMake PASS 729.88 seconds
MakeCheck PASS 12.15 seconds
MakeDistcheck PASS 153.41 seconds
CheckValgrind PASS 214.51 seconds
CheckSmatch PASS 318.96 seconds
bluezmakeextell PASS 100.20 seconds
IncrementalBuild PASS 657.52 seconds
ScanBuild PASS 895.89 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ] tools: avtest: Add reject-code option
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#46:
Some PTS tests like A2DP/SNK/AVP/BI-03-C, A2DP/SNK/AVP/BI-08-C , … request
WARNING:LONG_LINE: line length of 94 exceeds 80 columns
#63: FILE: tools/avtest.c:191:
+ int fragment, int reject_code)
WARNING:LONG_LINE_COMMENT: line length of 91 exceeds 80 columns
#72: FILE: tools/avtest.c:287:
+ buf[3] = reject_code ? reject_code : 0x13; /* SEP In Use */
WARNING:LONG_LINE: line length of 95 exceeds 80 columns
#81: FILE: tools/avtest.c:446:
+static void do_listen(const bdaddr_t *src, unsigned char reject, int fragment, int reject_code)
/github/workspace/src/src/13484955.patch total: 0 errors, 4 warnings, 78 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/13484955.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
prev parent reply other threads:[~2023-12-08 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 7:07 [PATCH BlueZ] tools: avtest: Add reject-code option Frédéric Danis
2023-12-08 8:28 ` 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=6572d3c0.050a0220.77b7b.2b11@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=frederic.danis@collabora.com \
--cc=linux-bluetooth@vger.kernel.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 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.