linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, silviu.barbulescu@nxp.com
Subject: RE: Add support for multiple BISes on the bcast source
Date: Mon, 12 Feb 2024 09:39:01 -0800 (PST)	[thread overview]
Message-ID: <65ca57b5.a70a0220.ee8a1.fc6a@mx.google.com> (raw)
In-Reply-To: <20240212153222.8191-2-silviu.barbulescu@nxp.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      2.12 seconds
GitLint                       PASS      1.38 seconds
BuildEll                      PASS      24.54 seconds
BluezMake                     PASS      725.68 seconds
MakeCheck                     PASS      11.46 seconds
MakeDistcheck                 PASS      162.50 seconds
CheckValgrind                 PASS      225.71 seconds
CheckSmatch                   PASS      327.98 seconds
bluezmakeextell               PASS      106.55 seconds
IncrementalBuild              PASS      4766.47 seconds
ScanBuild                     PASS      940.66 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-02-12 17:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 15:32 [PATCH BlueZ v2 0/7] [PATCH BlueZ v2 0/7] Add support for multiple BISes on the bcast source Silviu Florian Barbulescu
2024-02-12 15:32 ` [PATCH BlueZ v2 1/7] bap: Remove set lpac user data at bcast ep register Silviu Florian Barbulescu
2024-02-12 17:39   ` bluez.test.bot [this message]
2024-02-12 15:32 ` [PATCH BlueZ v2 2/7] shared/bap: Create multiple streams for the same pac Silviu Florian Barbulescu
2024-02-12 22:17   ` Luiz Augusto von Dentz
2024-02-12 15:32 ` [PATCH BlueZ v2 3/7] bap: Create a new endpoint for the next BIS configuration Silviu Florian Barbulescu
2024-02-12 15:32 ` [PATCH BlueZ v2 4/7] bap: Split bap_state and bap_connecting in two functions Silviu Florian Barbulescu
2024-02-12 15:32 ` [PATCH BlueZ v2 5/7] shared/bap: Check state of all streams with same BIG ID Silviu Florian Barbulescu
2024-02-12 15:32 ` [PATCH BlueZ v2 6/7] bap: Set generated BASE on all setups from the same BIG Silviu Florian Barbulescu
2024-02-12 15:32 ` [PATCH BlueZ v2 7/7] shared/bap: Generate one BIS BASE for config BIG ID 0xFF Silviu Florian Barbulescu
  -- strict thread matches above, loose matches on Subject: below --
2024-02-23 16:48 [PATCH BlueZ v4 1/5] shared/bap: Fix endpoint dir for the bcast source Silviu Florian Barbulescu
2024-02-23 18:51 ` Add support for multiple BISes on " bluez.test.bot
2024-02-15 21:23 [PATCH BlueZ v3 1/7] bap: Remove set lpac user data at bcast ep register Silviu Florian Barbulescu
2024-02-15 23:49 ` Add support for multiple BISes on the bcast source bluez.test.bot
2024-02-01 15:28 [PATCH BlueZ 1/7] bap: Remove set lpac user data at bcast ep register Silviu Florian Barbulescu
2024-02-01 17:37 ` Add support for multiple BISes on the bcast source 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=65ca57b5.a70a0220.ee8a1.fc6a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=silviu.barbulescu@nxp.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;
as well as URLs for NNTP newsgroup(s).