[dpdk-test-report] |WARNING| pw62493 [RFC 4/4] cryptodev: introduce rte_crypto_cpu_sym_session API
checkpatch at dpdk.org
checkpatch at dpdk.org
Tue Nov 5 19:43:58 CET 2019
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/62493
_coding style issues_
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#269: FILE: lib/librte_cryptodev/rte_cryptodev.h:1335:
+ * ^I^I^I(RTE_CRYPTO_OP_STATUS_* values)$
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#276: FILE: lib/librte_cryptodev/rte_cryptodev.h:1342:
++*/
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct rte_crypto_cpu_sym_session *' should also have an identifier name
#345: FILE: lib/librte_cryptodev/rte_cryptodev_pmd.h:547:
+ void (*clear)(struct rte_crypto_cpu_sym_session *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct rte_crypto_cpu_sym_session *' should also have an identifier name
#346: FILE: lib/librte_cryptodev/rte_cryptodev_pmd.h:548:
+ int (*process)(struct rte_crypto_cpu_sym_session *,
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct rte_crypto_sym_vec *' should also have an identifier name
#346: FILE: lib/librte_cryptodev/rte_cryptodev_pmd.h:548:
+ int (*process)(struct rte_crypto_cpu_sym_session *,
WARNING:FUNCTION_ARGUMENTS: function definition argument 'int32_t []' should also have an identifier name
#346: FILE: lib/librte_cryptodev/rte_cryptodev_pmd.h:548:
+ int (*process)(struct rte_crypto_cpu_sym_session *,
WARNING:FUNCTION_ARGUMENTS: function definition argument 'uint32_t' should also have an identifier name
#346: FILE: lib/librte_cryptodev/rte_cryptodev_pmd.h:548:
+ int (*process)(struct rte_crypto_cpu_sym_session *,
total: 0 errors, 7 warnings, 222 lines checked
Please only put __rte_experimental tags in headers (b/lib/librte_cryptodev/rte_cryptodev.c)
Please only put __rte_experimental tags in headers (b/lib/librte_cryptodev/rte_cryptodev.c)
Please only put __rte_experimental tags in headers (b/lib/librte_cryptodev/rte_cryptodev.c)
Please only put __rte_experimental tags in headers (b/lib/librte_cryptodev/rte_cryptodev.c)
More information about the test-report
mailing list