From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brian.gix@intel.com
Subject: RE: OOB Authentication improvements
Date: Wed, 19 May 2021 12:01:51 -0700 (PDT) [thread overview]
Message-ID: <60a5609f.1c69fb81.4ae7c.1067@mx.google.com> (raw)
In-Reply-To: <20210519182150.1680987-2-brian.gix@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1953 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=485239
---Test result---
Test Summary:
CheckPatch PASS 1.78 seconds
GitLint PASS 0.63 seconds
Prep - Setup ELL PASS 49.25 seconds
Build - Prep PASS 0.15 seconds
Build - Configure PASS 8.62 seconds
Build - Make PASS 214.90 seconds
Make Check PASS 8.97 seconds
Make Distcheck PASS 252.99 seconds
Build w/ext ELL - Configure PASS 8.65 seconds
Build w/ext ELL - Make PASS 202.95 seconds
Details
##############################
Test: CheckPatch - PASS
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
##############################
Test: GitLint - PASS
Desc: Run gitlint with rule in .gitlint
##############################
Test: Prep - Setup ELL - PASS
Desc: Clone, build, and install ELL
##############################
Test: Build - Prep - PASS
Desc: Prepare environment for build
##############################
Test: Build - Configure - PASS
Desc: Configure the BlueZ source tree
##############################
Test: Build - Make - PASS
Desc: Build the BlueZ source tree
##############################
Test: Make Check - PASS
Desc: Run 'make check'
##############################
Test: Make Distcheck - PASS
Desc: Run distcheck to check the distribution
##############################
Test: Build w/ext ELL - Configure - PASS
Desc: Configure BlueZ source with '--enable-external-ell' configuration
##############################
Test: Build w/ext ELL - Make - PASS
Desc: Build BlueZ source with '--enable-external-ell' configuration
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-05-19 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 18:21 [PATCH BlueZ v2 0/5] OOB Authentication improvements Brian Gix
2021-05-19 18:21 ` [PATCH BlueZ v2 1/5] mesh: Fix delivery of PB-ACK to acceptors Brian Gix
2021-05-19 18:30 ` Tedd Ho-Jeong An
2021-05-19 18:33 ` Gix, Brian
2021-05-19 19:01 ` bluez.test.bot [this message]
2021-05-19 18:21 ` [PATCH BlueZ v2 2/5] nesh: Normalize endian of public/private ECC keys Brian Gix
2021-05-19 18:21 ` [PATCH BlueZ v2 3/5] tools/mesh: Add all supported OOB methods to cfgclient Brian Gix
2021-05-19 18:21 ` [PATCH BlueZ v2 4/5] test/mesh: Add support for testing more OOB auth Brian Gix
2021-05-19 18:21 ` [PATCH BlueZ v2 5/5] mesh: Add single threading to prov-acp ob messaging Brian Gix
-- strict thread matches above, loose matches on Subject: below --
2021-05-19 19:09 [PATCH BlueZ v3 1/6] mesh: Fix delivery of PB-ACK to acceptors Brian Gix
2021-05-19 19:43 ` OOB Authentication improvements bluez.test.bot
2021-05-19 0:10 [PATCH BlueZ 1/4] mesh: Fix delivery of PB-ACK to acceptors Brian Gix
2021-05-19 1:38 ` OOB Authentication improvements 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=60a5609f.1c69fb81.4ae7c.1067@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;
as well as URLs for NNTP newsgroup(s).