linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, claudia.rosu@nxp.com
Subject: RE: Fix source+sink endpoint registration
Date: Wed, 25 Oct 2023 04:00:08 -0700 (PDT)	[thread overview]
Message-ID: <6538f538.9d0a0220.23110.cbd7@mx.google.com> (raw)
In-Reply-To: <20231025091853.18647-2-claudia.rosu@nxp.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.91 seconds
GitLint                       PASS      0.58 seconds
BuildEll                      PASS      28.99 seconds
BluezMake                     PASS      1029.55 seconds
MakeCheck                     PASS      12.15 seconds
MakeDistcheck                 PASS      179.83 seconds
CheckValgrind                 PASS      279.69 seconds
CheckSmatch                   PASS      373.18 seconds
bluezmakeextell               PASS      121.27 seconds
IncrementalBuild              PASS      1774.25 seconds
ScanBuild                     PASS      1137.70 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-10-25 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  9:18 [PATCH BlueZ v3 0/2] Fix source+sink endpoint registration Claudia Draghicescu
2023-10-25  9:18 ` [PATCH BlueZ v3 1/2] bap: " Claudia Draghicescu
2023-10-25 11:00   ` bluez.test.bot [this message]
2023-10-25  9:18 ` [PATCH BlueZ v3 2/2] " Claudia Draghicescu
  -- strict thread matches above, loose matches on Subject: below --
2023-10-19 13:54 [PATCH BlueZ v2 1/2] " Claudia Draghicescu
2023-10-19 16:00 ` 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=6538f538.9d0a0220.23110.cbd7@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=claudia.rosu@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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).