From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brian.gix@intel.com
Subject: RE: Add mesh testing support
Date: Wed, 31 Aug 2022 20:27:58 -0700 (PDT) [thread overview]
Message-ID: <631026be.370a0220.f7596.fe92@mx.google.com> (raw)
In-Reply-To: <20220831235932.290032-2-brian.gix@intel.com>
[-- 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=672998
---Test result---
Test Summary:
CheckPatch PASS 4.62 seconds
GitLint PASS 2.24 seconds
Prep - Setup ELL PASS 31.12 seconds
Build - Prep PASS 0.88 seconds
Build - Configure PASS 10.05 seconds
Build - Make PASS 950.81 seconds
Make Check PASS 12.98 seconds
Make Check w/Valgrind PASS 334.75 seconds
Make Distcheck PASS 277.41 seconds
Build w/ext ELL - Configure PASS 10.23 seconds
Build w/ext ELL - Make PASS 97.15 seconds
Incremental Build w/ patches PASS 231.34 seconds
Scan Build PASS 746.78 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-09-01 3:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 23:59 [PATCH BlueZ v4 0/2] Add mesh testing support Brian Gix
2022-08-31 23:59 ` [PATCH BlueZ v4 1/2] lib: Add mgmt opcodes and events for Mesh Brian Gix
2022-09-01 3:27 ` bluez.test.bot [this message]
2022-08-31 23:59 ` [PATCH BlueZ v4 2/2] tools: Add mesh-tester to test Kernel mesh support Brian Gix
2022-09-01 22:00 ` [PATCH BlueZ v4 0/2] Add mesh testing support patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2022-08-31 21:48 [PATCH BlueZ v3 1/2] lib: Add mgmt opcodes and events for Mesh Brian Gix
2022-08-31 23:17 ` Add mesh testing support bluez.test.bot
2022-08-31 20:11 [PATCH BlueZ 1/2] lib: Add mgmt opcodes and events for Mesh Brian Gix
2022-08-31 21:17 ` Add mesh testing support 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=631026be.370a0220.f7596.fe92@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