public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [BlueZ] main.conf: Add comment about LA Audio BAP UUIDs
Date: Wed, 02 Nov 2022 04:18:26 -0700 (PDT)	[thread overview]
Message-ID: <63625202.050a0220.a2974.53bf@mx.google.com> (raw)
In-Reply-To: <20221102101224.1463549-1-hadess@hadess.net>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.03 seconds
GitLint                       PASS      0.75 seconds
Prep - Setup ELL              PASS      33.82 seconds
Build - Prep                  PASS      0.98 seconds
Build - Configure             PASS      10.66 seconds
Build - Make                  PASS      1141.01 seconds
Make Check                    PASS      12.91 seconds
Make Check w/Valgrind         PASS      365.20 seconds
Make Distcheck                PASS      304.19 seconds
Build w/ext ELL - Configure   PASS      10.59 seconds
Build w/ext ELL - Make        PASS      109.91 seconds
Incremental Build w/ patches  PASS      0.00 seconds
Scan Build                    PASS      676.03 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-11-02 11:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 10:12 [BlueZ] main.conf: Add comment about LA Audio BAP UUIDs Bastien Nocera
2022-11-02 11:18 ` bluez.test.bot [this message]
2022-11-03 20:26 ` Luiz Augusto von Dentz
2022-11-09 15:55   ` Bastien Nocera
2022-11-18  2:31 ` bluez.test.bot
2022-11-18  4:05 ` bluez.test.bot
2022-11-18  4:43 ` bluez.test.bot
2022-11-18  5:13 ` bluez.test.bot
2022-11-18  5:33 ` bluez.test.bot
2022-11-18  6:04 ` bluez.test.bot
2022-11-19  3:47 ` bluez.test.bot
2022-11-19  5:32 ` 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=63625202.050a0220.a2974.53bf@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=hadess@hadess.net \
    --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