automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Przemyslaw Zegan <przemyslawx.zegan@intel.com>
Subject: |WARNING| pw115209 [dpdk-dev v2] app/test: random test vectors for Asymc RSA
Date: Wed, 17 Aug 2022 16:15:47 +0200 (CEST)	[thread overview]
Message-ID: <20220817141547.B3033121D40@dpdk.org> (raw)
In-Reply-To: <20220817141444.18437-1-przemyslawx.zegan@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/115209

_coding style issues_


WARNING:TYPO_SPELLING: 'enque' may be misspelled - perhaps 'enqueue'?
#492: FILE: app/test/test_cryptodev_asym_common.c:91:
+void ats_err_msg_enque(char *msg, uint32_t len, uint32_t line)

WARNING:TYPO_SPELLING: 'enque' may be misspelled - perhaps 'enqueue'?
#564: FILE: app/test/test_cryptodev_asym_common.h:40:
+void ats_err_msg_enque(char *msg, uint32_t len, uint32_t line);

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#671: FILE: app/test/test_cryptodev_asym_rsa.c:25:
+extern struct crypto_testsuite_params_asym testsuite_params_asym;

WARNING:TYPO_SPELLING: 'enque' may be misspelled - perhaps 'enqueue'?
#806: FILE: app/test/test_cryptodev_asym_rsa.c:160:
+		ats_err_msg_enque(test_msg, ASYM_TEST_MSG_LEN, __LINE__);

WARNING:SUSPECT_COMMA_SEMICOLON: Possible comma where semicolon could be used
#1122: FILE: app/test/test_cryptodev_asym_rsa_creator.c:138:
+	vct->padding = rule->padding,
+	vct->op_type_flags = rule->operation;

total: 0 errors, 5 warnings, 1204 lines checked

       reply	other threads:[~2022-08-17 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220817141444.18437-1-przemyslawx.zegan@intel.com>
2022-08-17 14:15 ` checkpatch [this message]
2022-08-17 15:20 ` |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=20220817141547.B3033121D40@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=przemyslawx.zegan@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).