From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hj.tedd.an@gmail.com
Subject: RE: [RFC,BlueZ,v2,1/2] emulator/btdev: Update the white list and resolving list size
Date: Wed, 16 Jun 2021 16:59:04 -0700 (PDT) [thread overview]
Message-ID: <60ca9048.1c69fb81.858bf.14b3@mx.google.com> (raw)
In-Reply-To: <20210616233716.1920026-1-hj.tedd.an@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2745 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=501957
---Test result---
Test Summary:
CheckPatch FAIL 1.04 seconds
GitLint PASS 0.21 seconds
Prep - Setup ELL PASS 40.50 seconds
Build - Prep PASS 0.10 seconds
Build - Configure PASS 7.09 seconds
Build - Make PASS 176.76 seconds
Make Check PASS 8.85 seconds
Make Distcheck PASS 209.42 seconds
Build w/ext ELL - Configure PASS 7.10 seconds
Build w/ext ELL - Make PASS 166.62 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
tools/mgmt-tester: Add LL Privacy test cases
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#322: FILE: tools/mgmt-tester.c:9315:
+ static const uint8_t le_add_to_white_list_param[] = {$
- total: 0 errors, 1 warnings, 1162 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
"[PATCH] tools/mgmt-tester: Add LL Privacy test cases" has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
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
prev parent reply other threads:[~2021-06-16 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 23:37 [RFC BlueZ PATCH v2 1/2] emulator/btdev: Update the white list and resolving list size Tedd Ho-Jeong An
2021-06-16 23:37 ` [RFC BlueZ PATCH v2 2/2] tools/mgmt-tester: Add LL Privacy test cases Tedd Ho-Jeong An
2021-06-16 23:59 ` 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=60ca9048.1c69fb81.858bf.14b3@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).