All of lore.kernel.org
 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] device: Add btd_ prefix to device_is_trusted
Date: Tue, 02 Aug 2022 10:21:43 -0700 (PDT)	[thread overview]
Message-ID: <62e95d27.620a0220.ee608.1eca@mx.google.com> (raw)
In-Reply-To: <20220802163441.2522333-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.79 seconds
GitLint                       PASS      1.08 seconds
Prep - Setup ELL              PASS      27.37 seconds
Build - Prep                  PASS      0.67 seconds
Build - Configure             PASS      8.50 seconds
Build - Make                  PASS      850.55 seconds
Make Check                    PASS      11.23 seconds
Make Check w/Valgrind         PASS      285.34 seconds
Make Distcheck                PASS      238.54 seconds
Build w/ext ELL - Configure   PASS      8.67 seconds
Build w/ext ELL - Make        PASS      82.08 seconds
Incremental Build w/ patches  PASS      195.11 seconds
Scan Build                    PASS      599.70 seconds



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2022-08-02 17:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 16:34 [PATCH BlueZ 1/2] device: Add btd_ prefix to device_is_trusted Luiz Augusto von Dentz
2022-08-02 16:34 ` [PATCH BlueZ 2/2] sixaxis: Fix fliping device.trusted automatically Luiz Augusto von Dentz
2022-08-02 17:21 ` bluez.test.bot [this message]
2022-08-02 19:50 ` [PATCH BlueZ 1/2] device: Add btd_ prefix to device_is_trusted 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=62e95d27.620a0220.ee608.1eca@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 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.