From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: |WARNING| pw115223 [PATCH 2/2] test/crypto: add ecdh tests
Date: Thu, 18 Aug 2022 09:15:17 +0200 (CEST) [thread overview]
Message-ID: <20220818071517.2FEB5121D40@dpdk.org> (raw)
In-Reply-To: <20220818060526.17343-3-arkadiuszx.kusztal@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/115223
_coding style issues_
WARNING:TYPO_SPELLING: 'Expeceted' may be misspelled - perhaps 'Expected'?
#143: FILE: app/test/test_cryptodev_asym.c:2422:
+ "Incorrect Alice public key length (X coeff) Received length = %lu Expeceted length = %lu
",
WARNING:TYPO_SPELLING: 'Expeceted' may be misspelled - perhaps 'Expected'?
#152: FILE: app/test/test_cryptodev_asym.c:2431:
+ "Incorrect Alice public key length (Y coeff) Received length = %lu Expeceted length = %lu
",
WARNING:TYPO_SPELLING: 'Expeceted' may be misspelled - perhaps 'Expected'?
#203: FILE: app/test/test_cryptodev_asym.c:2482:
+ "Incorrect Bob's public key length (X coeff) Received length = %lu Expeceted length = %lu
",
WARNING:TYPO_SPELLING: 'Expeceted' may be misspelled - perhaps 'Expected'?
#212: FILE: app/test/test_cryptodev_asym.c:2491:
+ "Incorrect Bob's public key length (Y coeff) Received length = %lu Expeceted length = %lu
",
WARNING:MISSING_EOF_NEWLINE: adding a line without newline at end of file
#602: FILE: app/test/test_cryptodev_ecdh_vectors.h:144:
+#endif
total: 0 errors, 5 warnings, 519 lines checked
Warning in app/test/test_cryptodev_asym.c:
Using %l format, prefer %PRI*64 if type is [u]int64_t
next parent reply other threads:[~2022-08-18 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220818060526.17343-3-arkadiuszx.kusztal@intel.com>
2022-08-18 7:15 ` checkpatch [this message]
2022-08-18 8:19 ` |FAILURE| " 0-day Robot
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=20220818071517.2FEB5121D40@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=arkadiuszx.kusztal@intel.com \
--cc=test-report@dpdk.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).