From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, silviu.barbulescu@nxp.com
Subject: RE: Add initial support for BAP broadcast source
Date: Tue, 30 May 2023 09:25:44 -0700 (PDT) [thread overview]
Message-ID: <64762388.050a0220.860bd.bc38@mx.google.com> (raw)
In-Reply-To: <20230530141339.100733-2-silviu.barbulescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 4008 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=752257
---Test result---
Test Summary:
CheckPatch FAIL 3.69 seconds
GitLint FAIL 1.58 seconds
BuildEll PASS 31.72 seconds
BluezMake PASS 988.14 seconds
MakeCheck PASS 12.89 seconds
MakeDistcheck PASS 176.46 seconds
CheckValgrind PASS 292.44 seconds
CheckSmatch PASS 390.18 seconds
bluezmakeextell PASS 118.95 seconds
IncrementalBuild PASS 3260.03 seconds
ScanBuild PASS 1198.85 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v3,2/4] Update bluetoothctl with support for broadcast source
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#99:
To test the current implementation use bluetoothctl with the following commands:
WARNING:LONG_LINE_STRING: line length of 86 exceeds 80 columns
#471: FILE: client/player.c:3769:
+ bt_shell_printf("Transport %s already in acquiring process\n",
WARNING:LONG_LINE_STRING: line length of 89 exceeds 80 columns
#483: FILE: client/player.c:3781:
+ bt_shell_printf("Link %s already in acquiring process\n",
WARNING:LONG_LINE: line length of 82 exceeds 80 columns
#485: FILE: client/player.c:3783:
+ return bt_shell_noninteractive_quit(EXIT_FAILURE);
/github/workspace/src/src/13260177.patch total: 0 errors, 4 warnings, 364 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/13260177.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.
[BlueZ,v3,4/4] Update BAP plugin with broadcast source support
WARNING:LONG_LINE: line length of 82 exceeds 80 columns
#431: FILE: profiles/audio/bap.c:1170:
+ iso_qos.bcast.sync_interval = ep->qos.bcast.sync_interval;
WARNING:LONG_LINE: line length of 82 exceeds 80 columns
#440: FILE: profiles/audio/bap.c:1179:
+ iso_qos.bcast.sync_cte_type = ep->qos.bcast.sync_cte_type;
/github/workspace/src/src/13260180.patch total: 0 errors, 2 warnings, 832 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/13260180.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
Output:
[BlueZ,v3,2/4] Update bluetoothctl with support for broadcast source
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
8: B1 Line exceeds max length (84>80): " transport.send /org/bluez/hci0/dev_00_00_00_00_00_00/pac_broadcast0/fd0 <file.wav>"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-05-30 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 14:13 [PATCH BlueZ v3 0/4] Add initial support for BAP broadcast source Silviu Florian Barbulescu
2023-05-30 14:13 ` [PATCH BlueZ v3 1/4] Split bt_bap_qos structure into unicast and broadcast structures Silviu Florian Barbulescu
2023-05-30 16:25 ` bluez.test.bot [this message]
2023-05-30 14:13 ` [PATCH BlueZ v3 2/4] Update bluetoothctl with support for broadcast source Silviu Florian Barbulescu
2023-05-30 14:13 ` [PATCH BlueZ v3 3/4] This adds the initial code for BAP " Silviu Florian Barbulescu
2023-05-30 14:13 ` [PATCH BlueZ v3 4/4] Update BAP plugin with broadcast source support Silviu Florian Barbulescu
2023-05-31 0:22 ` [PATCH BlueZ v3 0/4] Add initial support for BAP broadcast source Luiz Augusto von Dentz
2023-06-03 0:23 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2023-06-07 8:22 [PATCH v4 1/4] Split bt_bap_qos structure into unicast and broadcast structures Silviu Florian Barbulescu
2023-06-07 10:05 ` Add initial support for BAP broadcast source bluez.test.bot
2023-05-25 15:34 [PATCH v2 1/6] Update Docs " Silviu Florian Barbulescu
2023-05-25 18:41 ` Add initial support " bluez.test.bot
2023-05-23 14:34 [PATCH BlueZ 1/6] doc: Update Docs " Iulia Tanasescu
2023-05-23 15:14 ` Add initial support " 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=64762388.050a0220.860bd.bc38@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=silviu.barbulescu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox