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: [BlueZ,v3,1/2] bap: use MediaEndpoint related properties consistently
Date: Tue, 03 Oct 2023 13:50:52 -0700 (PDT)	[thread overview]
Message-ID: <651c7eac.c80a0220.601aa.3ff6@mx.google.com> (raw)
In-Reply-To: <530fedd2233740d401c67bc1470756c86cb578a2.1696360700.git.pav@iki.fi>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.17 seconds
GitLint                       PASS      1.98 seconds
BuildEll                      PASS      28.77 seconds
BluezMake                     PASS      897.30 seconds
MakeCheck                     PASS      12.03 seconds
MakeDistcheck                 PASS      163.96 seconds
CheckValgrind                 PASS      266.65 seconds
CheckSmatch                   PASS      359.83 seconds
bluezmakeextell               PASS      109.91 seconds
IncrementalBuild              PASS      1459.07 seconds
ScanBuild                     PASS      1105.26 seconds



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2023-10-03 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 19:19 [PATCH BlueZ v3 1/2] bap: use MediaEndpoint related properties consistently Pauli Virtanen
2023-10-03 19:19 ` [PATCH BlueZ v3 2/2] doc: clarify org.bluez.MediaEndpoint documentation Pauli Virtanen
2023-10-03 20:50 ` bluez.test.bot [this message]
2023-10-03 23:20 ` [PATCH BlueZ v3 1/2] bap: use MediaEndpoint related properties consistently patchwork-bot+bluetooth

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=651c7eac.c80a0220.601aa.3ff6@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.