From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brian.gix@intel.com
Subject: RE: OOB Authentication improvements
Date: Tue, 18 May 2021 18:38:20 -0700 (PDT) [thread overview]
Message-ID: <60a46c0c.1c69fb81.facac.b774@mx.google.com> (raw)
In-Reply-To: <20210519001027.1540720-2-brian.gix@intel.com>
[-- Attachment #1: Type: text/plain, Size: 4922 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=484617
---Test result---
Test Summary:
CheckPatch FAIL 0.88 seconds
GitLint PASS 0.45 seconds
Prep - Setup ELL PASS 45.27 seconds
Build - Prep PASS 0.13 seconds
Build - Configure PASS 7.80 seconds
Build - Make PASS 196.35 seconds
Make Check PASS 9.34 seconds
Make Distcheck PASS 231.73 seconds
Build w/ext ELL - Configure PASS 7.83 seconds
Build w/ext ELL - Make PASS 185.18 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
tools/mesh: Add all supported OOB methods to cfgclient
WARNING:STATIC_CONST_CHAR_ARRAY: static const char * array should probably be static const char * const
#18: FILE: tools/mesh-cfgclient.c:107:
+static const char *caps[] = {"static-oob",
ERROR:CODE_INDENT: code indent should use tabs where possible
#65: FILE: tools/mesh-cfgclient.c:594:
+ struct l_dbus_message *msg,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#65: FILE: tools/mesh-cfgclient.c:594:
+ struct l_dbus_message *msg,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#66: FILE: tools/mesh-cfgclient.c:595:
+ void *user_data)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#66: FILE: tools/mesh-cfgclient.c:595:
+ void *user_data)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#68: FILE: tools/mesh-cfgclient.c:597:
+ l_dbus_message_ref(msg);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#69: FILE: tools/mesh-cfgclient.c:598:
+ agent_input_request(HEXADECIMAL, 64, "Enter 512 bit Public Key",$
ERROR:CODE_INDENT: code indent should use tabs where possible
#70: FILE: tools/mesh-cfgclient.c:599:
+ agent_input_done, msg);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#70: FILE: tools/mesh-cfgclient.c:599:
+ agent_input_done, msg);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#71: FILE: tools/mesh-cfgclient.c:600:
+ return NULL;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#81: FILE: tools/mesh-cfgclient.c:641:
+ l_dbus_interface_method(iface, "PublicKey", 0, prompt_public_call,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#82: FILE: tools/mesh-cfgclient.c:642:
+ "ay", "", "data");$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#82: FILE: tools/mesh-cfgclient.c:642:
+ "ay", "", "data");$
- total: 4 errors, 9 warnings, 68 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.
NOTE: Whitespace errors detected.
You may wish to use scripts/cleanpatch or scripts/cleanfile
"[PATCH] tools/mesh: Add all supported OOB methods to cfgclient" 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
next prev parent reply other threads:[~2021-05-19 1:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 0:10 [PATCH BlueZ 0/4] OOB Authentication improvements Brian Gix
2021-05-19 0:10 ` [PATCH BlueZ 1/4] mesh: Fix delivery of PB-ACK to acceptors Brian Gix
2021-05-19 1:38 ` bluez.test.bot [this message]
2021-05-19 0:10 ` [PATCH BlueZ 2/4] nesh: Normalize endian of public/private ECC keys Brian Gix
2021-05-19 0:10 ` [PATCH BlueZ 3/4] tools/mesh: Add all supported OOB methods to cfgclient Brian Gix
2021-05-19 0:10 ` [PATCH BlueZ 4/4] test/mesh: Add support for testing more OOB auth Brian Gix
-- strict thread matches above, loose matches on Subject: below --
2021-05-19 18:21 [PATCH BlueZ v2 1/5] mesh: Fix delivery of PB-ACK to acceptors Brian Gix
2021-05-19 19:01 ` OOB Authentication improvements bluez.test.bot
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
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=60a46c0c.1c69fb81.facac.b774@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).