From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brian.gix@gmail.com
Subject: RE: Mesh v1.1 additions
Date: Fri, 20 Jan 2023 14:51:04 -0800 (PST) [thread overview]
Message-ID: <63cb1ad8.050a0220.eb359.8a0b@mx.google.com> (raw)
In-Reply-To: <20230120194731.90065-2-brian.gix@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5751 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=714256
---Test result---
Test Summary:
CheckPatch FAIL 9.32 seconds
GitLint FAIL 4.13 seconds
BuildEll PASS 26.61 seconds
BluezMake PASS 760.73 seconds
MakeCheck PASS 11.33 seconds
MakeDistcheck PASS 148.69 seconds
CheckValgrind PASS 239.29 seconds
CheckSmatch WARNING 320.71 seconds
bluezmakeextell PASS 95.92 seconds
IncrementalBuild PASS 6720.33 seconds
ScanBuild WARNING 942.59 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2,02/11] mesh: Add Remote Provisioning
WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#3306: FILE: mesh/remprv-server.c:238:
+ /* Fallthrough */
WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#3515: FILE: mesh/remprv-server.c:447:
+ /* Fallthrough */
WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#3519: FILE: mesh/remprv-server.c:451:
+ /* Fallthrough */
WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#3798: FILE: mesh/remprv-server.c:730:
+ /* Fallthrough */
/github/workspace/src/src/13110477.patch total: 0 errors, 4 warnings, 3742 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.
/github/workspace/src/src/13110477.patch 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.
[BlueZ,v2,07/11] mesh: Add Mesh Private Beacon server
WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#227: FILE: mesh/prvbeac-server.c:74:
+ /* Fallthrough */
WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#239: FILE: mesh/prvbeac-server.c:86:
+ /* Fallthrough */
WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#246: FILE: mesh/prvbeac-server.c:93:
+ /* Fallthrough */
/github/workspace/src/src/13110472.patch total: 0 errors, 3 warnings, 166 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.
/github/workspace/src/src/13110472.patch 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 - FAIL
Desc: Run gitlint
Output:
[BlueZ,v2,01/11] doc/mesh: Add Remote Provisioning DBus APIs
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
11: B3 Line contains hard tab characters (\t): " * Refresh Device Keys"
12: B3 Line contains hard tab characters (\t): " * Reassign Node Addresses"
13: B3 Line contains hard tab characters (\t): " * Refresh Node Composition"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
mesh/manager.c:113:35: warning: non-ANSI function declaration of function 'free_pending_add_call'mesh/crypto.c:1023:30: warning: non-ANSI function declaration of function 'mesh_crypto_check_avail'unit/test-mesh-crypto.c: note: in included file:
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
mesh/remprv-server.c:709:3: warning: Value stored to 'status' is never read
status = PB_REM_ERR_SUCCESS;
^ ~~~~~~~~~~~~~~~~~~
1 warning generated.
In file included from unit/test-mesh-crypto.c:20:
In file included from ./mesh/crypto.c:18:
In file included from ./ell/ell.h:1:
./ell/util.h:187:9: warning: 1st function call argument is an uninitialized value
return L_BE32_TO_CPU(L_GET_UNALIGNED((const uint32_t *) ptr));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./ell/util.h:89:28: note: expanded from macro 'L_BE32_TO_CPU'
#define L_BE32_TO_CPU(val) bswap_32(val)
^~~~~~~~~~~~~
/usr/include/byteswap.h:34:21: note: expanded from macro 'bswap_32'
#define bswap_32(x) __bswap_32 (x)
^~~~~~~~~~~~~~
unit/test-mesh-crypto.c:1337:3: warning: 7th function call argument is an uninitialized value
mesh_crypto_packet_decrypt(pkt, pkt_len,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
unit/test-mesh-crypto.c:1559:4: warning: 7th function call argument is an uninitialized value
mesh_crypto_packet_decrypt(packet, packet_len,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 warnings generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-01-20 22:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 19:47 [PATCH BlueZ v2 00/11] Mesh v1.1 additions Brian Gix
2023-01-20 19:47 ` [PATCH BlueZ v2 01/11] doc/mesh: Add Remote Provisioning DBus APIs Brian Gix
2023-01-20 22:51 ` bluez.test.bot [this message]
2023-01-20 19:47 ` [PATCH BlueZ v2 02/11] mesh: Add Remote Provisioning Brian Gix
2023-01-20 19:47 ` [PATCH BlueZ v2 03/11] tools/mesh: Optimize for multiple RPR servers and NPPI Brian Gix
2023-01-20 19:47 ` [PATCH BlueZ v2 04/11] mesh: Rename parameter list per crypto usage Brian Gix
2023-01-20 19:47 ` [PATCH BlueZ v2 05/11] unit/mesh: Add unit testing of Mesh Private Beaconing Brian Gix
2023-01-20 19:47 ` [PATCH BlueZ v2 06/11] mesh: Add storage of Mesh Private Beacon settings Brian Gix
2023-01-20 19:47 ` [PATCH BlueZ v2 07/11] mesh: Add Mesh Private Beacon server Brian Gix
2023-01-20 19:47 ` [PATCH BlueZ v2 08/11] mesh: Add Tx/Rx support of Mesh Private Beacons Brian Gix
2023-01-20 19:47 ` [PATCH BlueZ v2 09/11] mesh: Add internal Mesh Private Beacon model Brian Gix
2023-01-20 19:47 ` [PATCH BlueZ v2 10/11] tools/mesh: Add support for Mesh Private Beacons Brian Gix
2023-01-20 19:47 ` [PATCH BlueZ v2 11/11] mesh: Switch beaconing net key Brian Gix
-- strict thread matches above, loose matches on Subject: below --
2023-01-30 23:51 [PATCH BlueZ v5 01/14] doc/mesh: Add Remote Provisioning DBus APIs Brian Gix
2023-01-31 5:39 ` Mesh v1.1 additions bluez.test.bot
2023-01-24 20:26 [PATCH BlueZ v4 01/13] doc/mesh: Add Remote Provisioning DBus APIs Brian Gix
2023-01-25 0:25 ` Mesh v1.1 additions bluez.test.bot
2023-01-23 19:48 [PATCH BlueZ v3 01/11] doc/mesh: Add Remote Provisioning DBus APIs Brian Gix
2023-01-23 22:57 ` Mesh v1.1 additions bluez.test.bot
2023-01-19 23:57 [PATCH BlueZ 01/12] doc/mesh: Add Remote Provisioning DBus APIs Brian Gix
2023-01-20 4:12 ` Mesh v1.1 additions 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=63cb1ad8.050a0220.eb359.8a0b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=brian.gix@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).