linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, isak.westin@loytec.com
Subject: RE: Mesh: Fixes for PTS issues
Date: Thu, 06 Oct 2022 09:22:09 -0700 (PDT)	[thread overview]
Message-ID: <633f00b1.050a0220.96b53.62bc@mx.google.com> (raw)
In-Reply-To: <20221006145927.32731-2-isak.westin@loytec.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=683513

---Test result---

Test Summary:
CheckPatch                    PASS      6.47 seconds
GitLint                       PASS      4.32 seconds
Prep - Setup ELL              PASS      27.73 seconds
Build - Prep                  PASS      0.73 seconds
Build - Configure             PASS      8.76 seconds
Build - Make                  PASS      867.47 seconds
Make Check                    PASS      11.56 seconds
Make Check w/Valgrind         PASS      295.55 seconds
Make Distcheck                PASS      242.61 seconds
Build w/ext ELL - Configure   PASS      8.79 seconds
Build w/ext ELL - Make        PASS      85.61 seconds
Incremental Build w/ patches  PASS      602.70 seconds
Scan Build                    PASS      518.24 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-10-06 16:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 14:59 [PATCH BlueZ 0/6] Mesh: Fixes for PTS issues Isak Westin
2022-10-06 14:59 ` [PATCH BlueZ 1/6] mesh: Update Key Refresh flag after provision Isak Westin
2022-10-06 16:22   ` bluez.test.bot [this message]
2022-10-06 14:59 ` [PATCH BlueZ 2/6] mesh: provisionee: Handle unknown PDUs Isak Westin
2022-10-06 14:59 ` [PATCH BlueZ 3/6] mesh: provisionee: Handle failed provisioning Isak Westin
2022-10-06 14:59 ` [PATCH BlueZ 4/6] mesh: provisionee: Check prov start parameters Isak Westin
2022-10-06 14:59 ` [PATCH BlueZ 5/6] mesh: Keep canceled SAR data for at least 10 sec Isak Westin
2022-10-06 20:55   ` Gix, Brian
2022-10-07 13:33     ` Isak Westin
2022-10-07 14:56       ` Gix, Brian
2022-10-11 14:13         ` Isak Westin
2022-10-06 14:59 ` [PATCH BlueZ 6/6] mesh: Fix msg cache ring buffer Isak Westin
2022-10-06 20:47   ` Gix, Brian
2022-10-07  8:02     ` Isak Westin
2022-10-07 15:08   ` Gix, Brian
2022-10-06 21:00 ` [PATCH BlueZ 0/6] Mesh: Fixes for PTS issues patchwork-bot+bluetooth
2022-10-06 21:00 ` Gix, Brian
2022-10-07 15:10 ` 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=633f00b1.050a0220.96b53.62bc@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=isak.westin@loytec.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;
as well as URLs for NNTP newsgroup(s).