From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/5] shared/crypto: Adds bt_crypto_sih
Date: Thu, 22 Dec 2022 17:24:32 -0800 (PST) [thread overview]
Message-ID: <63a50350.c80a0220.e18f0.673c@mx.google.com> (raw)
In-Reply-To: <20221222224329.685837-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2548 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=706598
---Test result---
Test Summary:
CheckPatch FAIL 3.15 seconds
GitLint PASS 1.72 seconds
BuildEll PASS 32.60 seconds
BluezMake PASS 1106.86 seconds
MakeCheck PASS 12.66 seconds
MakeDistcheck PASS 179.90 seconds
CheckValgrind PASS 297.90 seconds
bluezmakeextell PASS 118.23 seconds
IncrementalBuild PASS 4631.99 seconds
ScanBuild PASS 1278.64 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,1/5] shared/crypto: Adds bt_crypto_sih
WARNING:REPEATED_WORD: Possible repeated word: 'is'
#80:
This adds bt_crypto_sih is is used to create a hash as stated on
/github/workspace/src/src/13080417.patch total: 0 errors, 1 warnings, 44 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/13080417.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,3/5] shared/crypto: Adds bt_crypto_sef
WARNING:REPEATED_WORD: Possible repeated word: 'is'
#84:
This adds bt_crypto_sef is is used to create a hash as stated on CSIS
/github/workspace/src/src/13080419.patch total: 0 errors, 1 warnings, 213 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/13080419.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.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-12-23 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 22:43 [PATCH BlueZ 1/5] shared/crypto: Adds bt_crypto_sih Luiz Augusto von Dentz
2022-12-22 22:43 ` [PATCH BlueZ 2/5] test-crypto: Add /crypto/sih test Luiz Augusto von Dentz
2022-12-22 22:43 ` [PATCH BlueZ 3/5] shared/crypto: Adds bt_crypto_sef Luiz Augusto von Dentz
2022-12-22 22:43 ` [PATCH BlueZ 4/5] test-crypto: Add /crypto/sef test Luiz Augusto von Dentz
2022-12-22 22:43 ` [PATCH BlueZ 5/5] monitor: Add support for decoding RSI Luiz Augusto von Dentz
2022-12-23 1:24 ` bluez.test.bot [this message]
2023-01-03 22:20 ` [PATCH BlueZ 1/5] shared/crypto: Adds bt_crypto_sih patchwork-bot+bluetooth
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=63a50350.c80a0220.e18f0.673c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.