From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Matan Azrad <matan@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw89085 [PATCH] cryptodev: support multiple cipher data-units
Date: Sun, 14 Mar 2021 13:19:33 +0100 (CET) [thread overview]
Message-ID: <20210314121933.3791D29C8@dpdk.org> (raw)
In-Reply-To: <1615724283-26149-1-git-send-email-matan@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/89085
_coding style issues_
WARNING:TYPO_SPELLING: 'MULITPLE' may be misspelled - perhaps 'MULTIPLE'?
#85:
RTE_CRYPTODEV_FF_CIPHER_MULITPLE_DATA_UNITS.
WARNING:TYPO_SPELLING: 'MULITPLE' may be misspelled - perhaps 'MULTIPLE'?
#140: FILE: doc/guides/cryptodevs/overview.rst:49:
+ - "CIPHER_MULITPLE_DATA_UNITS" feature flag means PMD support operations
WARNING:TYPO_SPELLING: 'MULITPLE' may be misspelled - perhaps 'MULTIPLE'?
#173: FILE: lib/librte_cryptodev/rte_crypto_sym.h:270:
+ /**< When RTE_CRYPTODEV_FF_CIPHER_MULITPLE_DATA_UNITS is enabled,
WARNING:TYPO_SPELLING: 'MULITPLE' may be misspelled - perhaps 'MULTIPLE'?
#207: FILE: lib/librte_cryptodev/rte_cryptodev.c:620:
+ case RTE_CRYPTODEV_FF_CIPHER_MULITPLE_DATA_UNITS:
WARNING:TYPO_SPELLING: 'MULITPLE' may be misspelled - perhaps 'MULTIPLE'?
#208: FILE: lib/librte_cryptodev/rte_cryptodev.c:621:
+ return "CIPHER_MULITPLE_DATA_UNITS";
WARNING:TYPO_SPELLING: 'MULITPLE' may be misspelled - perhaps 'MULTIPLE'?
#250: FILE: lib/librte_cryptodev/rte_cryptodev.h:480:
+#define RTE_CRYPTODEV_FF_CIPHER_MULITPLE_DATA_UNITS (1ULL << 25)
total: 0 errors, 6 warnings, 102 lines checked
parent reply other threads:[~2021-03-14 12:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1615724283-26149-1-git-send-email-matan@nvidia.com>]
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=20210314121933.3791D29C8@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=matan@nvidia.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).