Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, simon.mikuda@streamunlimited.com
Subject: RE: [BlueZ,v2,1/2] shared/bap: Initialize ucast/bcast IDs as unset
Date: Sun, 14 Jun 2026 04:05:18 -0700 (PDT)	[thread overview]
Message-ID: <6a2e8aee.27211789.1b7c5f.22ef@mx.google.com> (raw)
In-Reply-To: <20260614095520.1090106-1-simon.mikuda@streamunlimited.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.92 seconds
GitLint                       FAIL      0.63 seconds
BuildEll                      PASS      20.70 seconds
BluezMake                     PASS      656.66 seconds
MakeCheck                     PASS      18.62 seconds
MakeDistcheck                 PASS      246.18 seconds
CheckValgrind                 PASS      294.94 seconds
CheckSmatch                   WARNING   355.15 seconds
bluezmakeextell               PASS      183.39 seconds
IncrementalBuild              PASS      673.90 seconds
ScanBuild                     PASS      1033.04 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v2,2/2] shared/bap: Don't link server ucast streams before CIS IDs are assigned

1: T1 Title exceeds max length (86>80): "[BlueZ,v2,2/2] shared/bap: Don't link server ucast streams before CIS IDs are assigned"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/bap.c:317: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:317: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:317: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:317: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:317: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:317:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structures


https://github.com/bluez/bluez/pull/2229

---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2026-06-14 11:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 21:11 [PATCH BlueZ] shared/bap: Don't link ucast streams before CIS IDs are assigned Simon Mikuda
2026-06-09 22:03 ` Pauli Virtanen
2026-06-10  7:46   ` Simon Mikuda
2026-06-10 13:06     ` Luiz Augusto von Dentz
2026-06-14  9:55     ` [PATCH BlueZ v2 1/2] shared/bap: Initialize ucast/bcast IDs as unset Simon Mikuda
2026-06-14  9:55       ` [PATCH BlueZ v2 2/2] shared/bap: Don't link server ucast streams before CIS IDs are assigned Simon Mikuda
2026-06-14 10:24       ` [PATCH BlueZ v2 1/2] shared/bap: Initialize ucast/bcast IDs as unset Pauli Virtanen
2026-06-14 11:05       ` bluez.test.bot [this message]
2026-06-14 10:50     ` [PATCH BlueZ v3 " Simon Mikuda
2026-06-14 10:50       ` [PATCH BlueZ v3 2/2] shared/bap: Don't link server ucast streams before CIS IDs are assigned Simon Mikuda
2026-06-14 13:03       ` [BlueZ,v3,1/2] shared/bap: Initialize ucast/bcast IDs as unset bluez.test.bot
2026-06-09 23:00 ` [BlueZ] shared/bap: Don't link ucast streams before CIS IDs are assigned 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=6a2e8aee.27211789.1b7c5f.22ef@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=simon.mikuda@streamunlimited.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