Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, vlad.pruteanu@nxp.com
Subject: RE: bap: Use defer setup when syncing to a BIS source
Date: Mon, 11 Sep 2023 00:40:49 -0700 (PDT)	[thread overview]
Message-ID: <64fec481.0c0a0220.fc9e2.9de5@mx.google.com> (raw)
In-Reply-To: <20230911061624.30600-2-vlad.pruteanu@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=782813

---Test result---

Test Summary:
CheckPatch                    PASS      0.57 seconds
GitLint                       PASS      0.36 seconds
BuildEll                      PASS      28.20 seconds
BluezMake                     PASS      934.65 seconds
MakeCheck                     PASS      12.39 seconds
MakeDistcheck                 PASS      162.65 seconds
CheckValgrind                 PASS      264.44 seconds
CheckSmatch                   PASS      356.71 seconds
bluezmakeextell               PASS      108.14 seconds
IncrementalBuild              PASS      765.23 seconds
ScanBuild                     PASS      1121.72 seconds



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2023-09-11  7:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11  6:16 [PATCH BlueZ v2 0/1] bap: Use defer setup when syncing to a BIS source Vlad Pruteanu
2023-09-11  6:16 ` [PATCH BlueZ v2 1/1] " Vlad Pruteanu
2023-09-11  7:04   ` Ziyang Xuan (William)
2023-09-11  8:39     ` Vlad Pruteanu
2023-09-11  7:40   ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-12  6:55 [PATCH BlueZ v4 " Vlad Pruteanu
2023-09-12  8:11 ` bluez.test.bot
2023-09-08 11:12 [PATCH BlueZ 1/1] " Vlad Pruteanu
2023-09-08 12:46 ` 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=64fec481.0c0a0220.fc9e2.9de5@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vlad.pruteanu@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