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: transport: distinguish BAP mic and playback volumes
Date: Sun, 04 Jan 2026 13:49:56 -0800 (PST)	[thread overview]
Message-ID: <695ae084.050a0220.97868.ec10@mx.google.com> (raw)
In-Reply-To: <ce1ecf069f0856ff58471bbc39c6e38ad4acf0a9.1767559459.git.pav@iki.fi>

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

---Test result---

Test Summary:
CheckPatch                    PENDING   0.30 seconds
GitLint                       PENDING   0.27 seconds
BuildEll                      PASS      20.50 seconds
BluezMake                     PASS      658.19 seconds
MakeCheck                     PASS      22.50 seconds
MakeDistcheck                 PASS      245.23 seconds
CheckValgrind                 PASS      306.15 seconds
CheckSmatch                   WARNING   354.28 seconds
bluezmakeextell               PASS      183.48 seconds
IncrementalBuild              PENDING   0.25 seconds
ScanBuild                     PASS      1048.98 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/bap.c:312: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:312: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:312:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structures
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-01-04 21:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-04 20:51 [PATCH BlueZ 0/3] transport: distinguish BAP mic and playback volumes Pauli Virtanen
2026-01-04 20:51 ` [PATCH BlueZ 1/3] shared/bap: add bt_bap_stream_is_server Pauli Virtanen
2026-01-04 21:49   ` bluez.test.bot [this message]
2026-01-05 18:45   ` Luiz Augusto von Dentz
2026-01-05 19:09     ` Pauli Virtanen
2026-01-05 19:29       ` Luiz Augusto von Dentz
2026-01-05 20:20         ` Pauli Virtanen
2026-01-04 20:51 ` [PATCH BlueZ 2/3] transport: clean up volume set/get for A2DP and VCP Pauli Virtanen
2026-01-04 20:51 ` [PATCH BlueZ 3/3] transport: distinguish BAP mic and playback volumes Pauli Virtanen
  -- strict thread matches above, loose matches on Subject: below --
2026-01-05 21:07 [PATCH BlueZ v2 1/2] transport: clean up volume set/get for A2DP and VCP Pauli Virtanen
2026-01-05 22:04 ` transport: distinguish BAP mic and playback volumes 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=695ae084.050a0220.97868.ec10@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.