All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, VAnPushkarev@salutedevices.com
Subject: RE: Introduce option to limit A2DP channels
Date: Mon, 29 Jan 2024 14:18:06 -0800 (PST)	[thread overview]
Message-ID: <65b8241e.050a0220.37eb2.8f55@mx.google.com> (raw)
In-Reply-To: <20240129204154.95773-2-VAnPushkarev@salutedevices.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.20 seconds
GitLint                       PASS      0.64 seconds
BuildEll                      PASS      24.30 seconds
BluezMake                     PASS      744.06 seconds
MakeCheck                     PASS      11.58 seconds
MakeDistcheck                 PASS      164.00 seconds
CheckValgrind                 PASS      227.32 seconds
CheckSmatch                   PASS      333.77 seconds
bluezmakeextell               PASS      109.57 seconds
IncrementalBuild              PASS      1374.21 seconds
ScanBuild                     PASS      955.44 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v1,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
#145: FILE: src/main.c:165:
+static const char *a2dp_options[] = {

/github/workspace/src/src/13536361.patch total: 0 errors, 1 warnings, 75 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/13536361.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,v1,2/2] a2dp: Reject connection when the channel limit is exceeded
WARNING:LONG_LINE: line length of 90 exceeds 80 columns
#118: FILE: profiles/audio/a2dp.c:2553:
+				queue_length(server->channels) > btd_opts.a2dp.channels) {

WARNING:LONG_LINE_STRING: line length of 81 exceeds 80 columns
#120: FILE: profiles/audio/a2dp.c:2555:
+		DBG("Reject current connection, A2DP channel limit exceeded: %d",

/github/workspace/src/src/13536360.patch total: 0 errors, 2 warnings, 14 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/13536360.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


  reply	other threads:[~2024-01-29 22:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 20:41 [PATCH BlueZ v1 0/2] Introduce option to limit A2DP channels Victor Pushkarev
2024-01-29 20:41 ` [PATCH BlueZ v1 1/2] main.conf: " Victor Pushkarev
2024-01-29 22:18   ` bluez.test.bot [this message]
2024-01-29 20:41 ` [PATCH BlueZ v1 2/2] a2dp: Reject connection when the channel limit is exceeded Victor Pushkarev
2024-01-29 21:06   ` Luiz Augusto von Dentz
  -- strict thread matches above, loose matches on Subject: below --
2024-11-07 22:01 [PATCH BlueZ 1/2] main.conf: Introduce option to limit A2DP channels Victor Pushkarev
2024-11-08  0:09 ` 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=65b8241e.050a0220.37eb2.8f55@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.