From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hj.tedd.an@gmail.com
Subject: RE: [BlueZ,1/4] tools/btmgmt: Add device flags commands
Date: Tue, 25 May 2021 19:04:48 -0700 (PDT) [thread overview]
Message-ID: <60adacc0.1c69fb81.9ef07.474f@mx.google.com> (raw)
In-Reply-To: <20210526002024.412237-1-hj.tedd.an@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2687 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=488499
---Test result---
Test Summary:
CheckPatch PASS 1.03 seconds
GitLint FAIL 0.43 seconds
Prep - Setup ELL PASS 40.41 seconds
Build - Prep PASS 0.10 seconds
Build - Configure PASS 7.11 seconds
Build - Make PASS 174.58 seconds
Make Check PASS 8.92 seconds
Make Distcheck PASS 206.40 seconds
Build w/ext ELL - Configure PASS 7.13 seconds
Build w/ext ELL - Make PASS 164.19 seconds
Details
##############################
Test: CheckPatch - PASS
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
tools/btmgmt: Add device flags commands
8: B3 Line contains hard tab characters (\t): " -t type Address Type"
9: B3 Line contains hard tab characters (\t): " 0 BR/EDR"
10: B3 Line contains hard tab characters (\t): " 1 LE Public"
11: B3 Line contains hard tab characters (\t): " 2 LE Random"
14: B3 Line contains hard tab characters (\t): " -t type Address Type"
15: B3 Line contains hard tab characters (\t): " 0 BR/EDR"
16: B3 Line contains hard tab characters (\t): " 1 LE Public"
17: B3 Line contains hard tab characters (\t): " 2 LE Random"
18: B3 Line contains hard tab characters (\t): " -f flags Device flag."
19: B3 Line contains hard tab characters (\t): " 1 Remote Wake Enable"
##############################
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
prev parent reply other threads:[~2021-05-26 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 0:20 [BlueZ PATCH 1/4] tools/btmgmt: Add device flags commands Tedd Ho-Jeong An
2021-05-26 0:20 ` [BlueZ PATCH 2/4] lib: Align mgmt header with document Tedd Ho-Jeong An
2021-05-26 0:20 ` [BlueZ PATCH 3/4] tools/mgmt-tester: Print hexdump if mgmt event parameters not match Tedd Ho-Jeong An
2021-05-26 0:20 ` [BlueZ PATCH 4/4] tools/mgmt-tester: Add test cases for get/set device flags Tedd Ho-Jeong An
2021-05-26 2:04 ` bluez.test.bot [this message]
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=60adacc0.1c69fb81.9ef07.474f@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;
as well as URLs for NNTP newsgroup(s).