From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hj.tedd.an@gmail.com
Subject: RE: [BlueZ,v2] monitor: Add Intel read supported VS features command
Date: Fri, 16 Apr 2021 18:30:34 -0700 (PDT) [thread overview]
Message-ID: <607a3a3a.1c69fb81.45b05.5b64@mx.google.com> (raw)
In-Reply-To: <20210417003446.628078-1-hj.tedd.an@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2296 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=468919
---Test result---
Test Summary:
CheckPatch PASS 0.37 seconds
GitLint PASS 0.12 seconds
Prep - Setup ELL PASS 51.15 seconds
Build - Prep PASS 0.15 seconds
Build - Configure PASS 8.88 seconds
Build - Make PASS 224.08 seconds
Make Check PASS 9.67 seconds
Make Dist PASS 13.41 seconds
Make Dist - Configure PASS 5.66 seconds
Make Dist - Make PASS 91.53 seconds
Build w/ext ELL - Configure PASS 9.04 seconds
Build w/ext ELL - Make PASS 208.59 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 Dist - PASS
Desc: Run 'make dist' and build the distribution tarball
##############################
Test: Make Dist - Configure - PASS
Desc: Configure the source from distribution tarball
##############################
Test: Make Dist - Make - PASS
Desc: Build the source from distribution tarball
##############################
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-04-17 1:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Tedd Ho-Jeong An <tedd.an@intel.com>
2021-04-14 4:38 ` [BlueZ] monitor: Fix the incorrect vendor name Tedd Ho-Jeong An
2021-04-14 5:07 ` bluez.test.bot
2021-04-14 10:08 ` Marcel Holtmann
2021-04-15 2:25 ` An, Tedd
2021-04-15 3:47 ` Archie Pusaka
2021-04-15 4:34 ` Tedd Ho-Jeong An
2021-04-16 5:23 ` Marcel Holtmann
2021-04-15 1:48 ` [RFC BlueZ v2] " Tedd Ho-Jeong An
2021-04-15 2:35 ` [RFC,BlueZ,v2] " bluez.test.bot
2021-04-16 5:56 ` [BlueZ PATCH] monitor: Update manpage Tedd Ho-Jeong An
2021-04-16 6:43 ` [BlueZ] " bluez.test.bot
2021-04-16 20:06 ` [BlueZ PATCH] monitor: Add Intel read supported VS features command Tedd Ho-Jeong An
2021-04-16 20:39 ` [BlueZ] " bluez.test.bot
2021-04-17 0:34 ` [BlueZ v2] " Tedd Ho-Jeong An
2021-04-17 1:30 ` bluez.test.bot [this message]
2021-04-19 13:01 ` Marcel Holtmann
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=607a3a3a.1c69fb81.45b05.5b64@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hj.tedd.an@gmail.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