From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, VAnPushkarev@salutedevices.com
Subject: RE: Introduce option to limit A2DP channels
Date: Thu, 07 Nov 2024 16:09:08 -0800 (PST) [thread overview]
Message-ID: <672d56a4.d40a0220.386e38.514f@mx.google.com> (raw)
In-Reply-To: <20241107220121.97417-2-VAnPushkarev@salutedevices.com>
[-- Attachment #1: Type: text/plain, Size: 3349 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=907547
---Test result---
Test Summary:
CheckPatch FAIL 1.02 seconds
GitLint PASS 0.63 seconds
BuildEll PASS 25.51 seconds
BluezMake PASS 1739.17 seconds
MakeCheck PASS 12.98 seconds
MakeDistcheck PASS 178.52 seconds
CheckValgrind PASS 252.44 seconds
CheckSmatch PASS 356.62 seconds
bluezmakeextell PASS 122.75 seconds
IncrementalBuild PASS 3101.50 seconds
ScanBuild WARNING 1008.31 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,1/2] main.conf: Introduce option to limit A2DP channels
WARNING:STATIC_CONST_CHAR_ARRAY: static const char * array should probably be static const char * const
#140: FILE: src/main.c:173:
+static const char *a2dp_options[] = {
/github/workspace/src/src/13867230.patch total: 0 errors, 1 warnings, 74 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/13867230.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,2/2] a2dp: Reject incoming connection when channel limit is exceeded
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#116: FILE: profiles/audio/a2dp.c:721:
+ /* Reject connection from SEP
+ * and clear configuration.
WARNING:LONG_LINE: line length of 95 exceeds 80 columns
#118: FILE: profiles/audio/a2dp.c:723:
+ DBG("Reject connection from %s", device_get_path(setup->chan->device));
WARNING:LONG_LINE: line length of 95 exceeds 80 columns
#119: FILE: profiles/audio/a2dp.c:724:
+ a2dp_sep->endpoint->clear_configuration(a2dp_sep, a2dp_sep->user_data);
/github/workspace/src/src/13867231.patch total: 0 errors, 3 warnings, 50 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/13867231.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:
profiles/audio/media.c:1059:7: warning: Use of memory after it is freed
if (req->cb != pac_select_cb) {
^~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-11-08 0:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 22:01 [PATCH BlueZ 0/2] Introduce option to limit A2DP channels Victor Pushkarev
2024-11-07 22:01 ` [PATCH BlueZ 1/2] main.conf: " Victor Pushkarev
2024-11-08 0:09 ` bluez.test.bot [this message]
2024-11-07 22:01 ` [PATCH BlueZ 2/2] a2dp: Reject incoming connection when channel limit is exceeded Victor Pushkarev
2024-11-07 23:01 ` Luiz Augusto von Dentz
2024-12-05 10:51 ` Victor Pushkarev
-- strict thread matches above, loose matches on Subject: below --
2024-01-29 20:41 [PATCH BlueZ v1 1/2] main.conf: Introduce option to limit A2DP channels Victor Pushkarev
2024-01-29 22:18 ` 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=672d56a4.d40a0220.386e38.514f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=VAnPushkarev@salutedevices.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.