From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-test-report] |WARNING| pw66888 [PATCH] cryptodev: version rte_cryptodev_info_get function
Date: Wed, 18 Mar 2020 21:45:37 +0100 (CET) [thread overview]
Message-ID: <20200318204537.A40222BF9@dpdk.org> (raw)
In-Reply-To: <20200318204136.10508-1-arkadiuszx.kusztal@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/66888
_coding style issues_
WARNING:LONG_LINE_COMMENT: line over 90 characters
#155: FILE: lib/librte_cryptodev/rte_cryptodev.c:1172:
+ * error case - no memory to store the trimmed list,
WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#167: FILE: lib/librte_cryptodev/rte_cryptodev.c:1184:
+ if (!(capability->op ==
WARNING:LONG_LINE: line over 90 characters
#168: FILE: lib/librte_cryptodev/rte_cryptodev.c:1185:
+ RTE_CRYPTO_OP_TYPE_SYMMETRIC
WARNING:LONG_LINE: line over 90 characters
#169: FILE: lib/librte_cryptodev/rte_cryptodev.c:1186:
+ && capability->sym.xform_type ==
WARNING:LONG_LINE: line over 90 characters
#171: FILE: lib/librte_cryptodev/rte_cryptodev.c:1188:
+ && capability->sym.aead.algo >=
WARNING:LONG_LINE: line over 90 characters
#172: FILE: lib/librte_cryptodev/rte_cryptodev.c:1189:
+ RTE_CRYPTO_AEAD_CHACHA20_POLY1305)) {
WARNING:LONG_LINE: line over 90 characters
#173: FILE: lib/librte_cryptodev/rte_cryptodev.c:1190:
+ capability_copies[dev_id][counter++] =
total: 0 errors, 7 warnings, 171 lines checked
ERROR: symbol rte_cryptodev_info_get is added in the DPDK_20.05 section, but is expected to be added in the EXPERIMENTAL section of the version map
next parent reply other threads:[~2020-03-18 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200318204136.10508-1-arkadiuszx.kusztal@intel.com>
2020-03-18 20:45 ` checkpatch [this message]
2020-03-18 22:09 ` [dpdk-test-report] |WARNING| pw66888 " 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=20200318204537.A40222BF9@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).