All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ] shared/bap: improve channel allocation logic in bt_bap_select()
Date: Sat, 27 Jul 2024 06:51:43 -0700 (PDT)	[thread overview]
Message-ID: <66a4fb6f.050a0220.7d9f0.a366@mx.google.com> (raw)
In-Reply-To: <81bcbcb669a6f329b7900fb0f6ff0c469ec7201f.1722082241.git.pav@iki.fi>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.54 seconds
GitLint                       FAIL      0.55 seconds
BuildEll                      PASS      24.57 seconds
BluezMake                     PASS      1648.54 seconds
MakeCheck                     PASS      13.33 seconds
MakeDistcheck                 PASS      178.24 seconds
CheckValgrind                 PASS      252.49 seconds
CheckSmatch                   WARNING   355.20 seconds
bluezmakeextell               PASS      119.94 seconds
IncrementalBuild              PASS      1421.31 seconds
ScanBuild                     PASS      1003.41 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ] shared/bap: improve channel allocation logic in bt_bap_select()

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
13: B1 Line exceeds max length (83>80): "    src/shared/bap.c:foreach_pacs_char() PAC Supported Context found: handle 0x0053"
71: B2 Line has trailing whitespace: "    "
77: B2 Line has trailing whitespace: "    "
83: B2 Line has trailing whitespace: "    "
87: B2 Line has trailing whitespace: "    "
90: B2 Line has trailing whitespace: "    "
93: B2 Line has trailing whitespace: "    "
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/bap.c:283:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:283:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:283:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structures


---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-07-27 13:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-27 12:13 [PATCH BlueZ] shared/bap: improve channel allocation logic in bt_bap_select() Pauli Virtanen
2024-07-27 13:51 ` bluez.test.bot [this message]
2024-07-29 11:38 ` Luiz Augusto von Dentz

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=66a4fb6f.050a0220.7d9f0.a366@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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.