From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-test-report] |WARNING| pw68633 [PATCH v2] cryptodev: version rte_cryptodev_info_get function
Date: Thu, 16 Apr 2020 10:15:00 +0200 (CEST) [thread overview]
Message-ID: <20200416081500.6ED8D1DAE6@dpdk.org> (raw)
In-Reply-To: <20200416081232.6024-1-arkadiuszx.kusztal@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/68633
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:LONG_LINE_COMMENT: line over 90 characters
#219: FILE: lib/librte_cryptodev/rte_cryptodev.c:1212:
+ * error case - no memory to store the trimmed list,
WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#231: FILE: lib/librte_cryptodev/rte_cryptodev.c:1224:
+ if (!(capability->op ==
WARNING:LONG_LINE: line over 90 characters
#232: FILE: lib/librte_cryptodev/rte_cryptodev.c:1225:
+ RTE_CRYPTO_OP_TYPE_SYMMETRIC
WARNING:LONG_LINE: line over 90 characters
#233: FILE: lib/librte_cryptodev/rte_cryptodev.c:1226:
+ && capability->sym.xform_type ==
WARNING:LONG_LINE: line over 90 characters
#235: FILE: lib/librte_cryptodev/rte_cryptodev.c:1228:
+ && capability->sym.aead.algo >=
WARNING:LONG_LINE: line over 90 characters
#236: FILE: lib/librte_cryptodev/rte_cryptodev.c:1229:
+ RTE_CRYPTO_AEAD_CHACHA20_POLY1305)) {
WARNING:LONG_LINE: line over 90 characters
#237: FILE: lib/librte_cryptodev/rte_cryptodev.c:1230:
+ capability_copies[dev_id][counter++] =
total: 0 errors, 7 warnings, 259 lines checked
ERROR: symbol rte_cryptodev_info_get is added in the DPDK_20.0.2 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_cryptodev_sym_capability_get is added in the DPDK_20.0.2 section, but is expected to be added in the EXPERIMENTAL section of the version map
parent reply other threads:[~2020-04-16 8:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200416081232.6024-1-arkadiuszx.kusztal@intel.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=20200416081500.6ED8D1DAE6@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).