linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/2] main.conf: Split Kernel Experimental UUIDs from Experimental
Date: Tue, 14 Jun 2022 16:57:25 -0700 (PDT)	[thread overview]
Message-ID: <62a92065.1c69fb81.f862c.6307@mx.google.com> (raw)
In-Reply-To: <20220614215609.596687-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      2.32 seconds
GitLint                       PASS      1.58 seconds
Prep - Setup ELL              PASS      41.64 seconds
Build - Prep                  PASS      0.59 seconds
Build - Configure             PASS      8.10 seconds
Build - Make                  PASS      1198.21 seconds
Make Check                    PASS      11.70 seconds
Make Check w/Valgrind         PASS      441.76 seconds
Make Distcheck                PASS      228.39 seconds
Build w/ext ELL - Configure   PASS      8.13 seconds
Build w/ext ELL - Make        PASS      1183.39 seconds
Incremental Build with patchesPASS      2414.49 seconds



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2022-06-14 23:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 21:56 [PATCH BlueZ 1/2] main.conf: Split Kernel Experimental UUIDs from Experimental Luiz Augusto von Dentz
2022-06-14 21:56 ` [PATCH BlueZ 2/2] bluetoothd.rst: Document -K/--kernel option Luiz Augusto von Dentz
2022-06-14 23:57 ` bluez.test.bot [this message]
2022-06-16 19:40 ` [PATCH BlueZ 1/2] main.conf: Split Kernel Experimental UUIDs from Experimental 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=62a92065.1c69fb81.f862c.6307@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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).