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, brian.gix@intel.com
Subject: RE: Mesh demon switched to using kernel Mesh MGMT
Date: Fri, 23 Sep 2022 12:24:50 -0700 (PDT)	[thread overview]
Message-ID: <632e0802.9d0a0220.dbaf0.26e8@mx.google.com> (raw)
In-Reply-To: <20220923180018.815614-2-brian.gix@intel.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      3.72 seconds
GitLint                       PASS      1.59 seconds
Prep - Setup ELL              PASS      32.34 seconds
Build - Prep                  PASS      0.80 seconds
Build - Configure             PASS      10.16 seconds
Build - Make                  PASS      962.18 seconds
Make Check                    PASS      13.10 seconds
Make Check w/Valgrind         PASS      346.94 seconds
Make Distcheck                PASS      288.02 seconds
Build w/ext ELL - Configure   PASS      10.29 seconds
Build w/ext ELL - Make        PASS      101.50 seconds
Incremental Build w/ patches  PASS      239.82 seconds
Scan Build                    PASS      663.36 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-09-23 19:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 18:00 [PATCH BlueZ v5 0/2] Mesh demon switched to using kernel Mesh MGMT Brian Gix
2022-09-23 18:00 ` [PATCH BlueZ v5 1/2] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-23 19:24   ` bluez.test.bot [this message]
2022-09-23 18:00 ` [PATCH BlueZ v5 2/2] mesh: Add new kernel MGMT based IO transport Brian Gix
2022-09-26 20:20 ` [PATCH BlueZ v5 0/2] Mesh demon switched to using kernel Mesh MGMT patchwork-bot+bluetooth
  -- strict thread matches above, loose matches on Subject: below --
2022-09-22 22:31 [PATCH BlueZ v4 1/2] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-22 23:26 ` Mesh demon switched to using kernel Mesh MGMT bluez.test.bot
2022-09-22 21:40 [PATCH BlueZ v3 1/2] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-22 22:26 ` Mesh demon switched to using kernel Mesh MGMT bluez.test.bot
2022-09-22 21:38 [PATCH BlueZ v2 1/2] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-22 22:24 ` Mesh demon switched to using kernel Mesh MGMT bluez.test.bot
2022-09-22 20:38 [PATCH BlueZ 1/4] mgmt: Add support for Mesh in the kernel Brian Gix
2022-09-22 21:32 ` Mesh demon switched to using kernel Mesh MGMT 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=632e0802.9d0a0220.dbaf0.26e8@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=brian.gix@intel.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