From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw31138 [PATCH RFC v2 4/7] lib/librte_vhost: add vhost_user backend support
Date: Thu, 2 Nov 2017 21:12:15 +0100 (CET) [thread overview]
Message-ID: <20171102201215.BA4931B689@dpdk.org> (raw)
In-Reply-To: <20171102201059.2803-5-roy.fan.zhang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/31138
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#146: FILE: lib/librte_vhost/rte_vhost_crypto.h:110:
+ unsigned nb_elts, unsigned cache_size, int socket_id);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#146: FILE: lib/librte_vhost/rte_vhost_crypto.h:110:
+ unsigned nb_elts, unsigned cache_size, int socket_id);
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#247: FILE: lib/librte_vhost/vhost_crypto.c:55:
+#define INHDR_LEN ^I^I(sizeof(struct virtio_crypto_inhdr))$
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#280: FILE: lib/librte_vhost/vhost_crypto.c:88:
+#define GPA_TO_VVA(t, m, a) \
+ (t)(uintptr_t)rte_vhost_gpa_to_vva(m, a)
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#284: FILE: lib/librte_vhost/vhost_crypto.c:92:
+#define REQ_OP_OFFSET ^I^I(IV_OFFSET + VHOST_CRYPTO_MAX_IV_LEN)$
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#432: FILE: lib/librte_vhost/vhost_crypto.c:240:
+static int
+transform_cipher_param(struct rte_crypto_sym_xform *xform,
+ VhostUserCryptoSessionParam *param) {
ERROR:SPACING: space required before the open parenthesis '('
#520: FILE: lib/librte_vhost/vhost_crypto.c:328:
+ switch(sess_param->op_type) {
WARNING:BRACES: braces {} are not necessary for single statement blocks
#701: FILE: lib/librte_vhost/vhost_crypto.c:509:
+ if (unlikely(to_move)) {
+ left -= to_move;
+ }
ERROR:SPACING: space prohibited before that ',' (ctx:WxV)
#839: FILE: lib/librte_vhost/vhost_crypto.c:647:
+ rte_hexdump(stdout ,"", dst, to_write);
^
ERROR:SPACING: space required after that ',' (ctx:WxV)
#839: FILE: lib/librte_vhost/vhost_crypto.c:647:
+ rte_hexdump(stdout ,"", dst, to_write);
^
ERROR:SPACING: space prohibited before that ',' (ctx:WxV)
#850: FILE: lib/librte_vhost/vhost_crypto.c:658:
+ rte_hexdump(stdout ,"", dst, to_write);
^
ERROR:SPACING: space required after that ',' (ctx:WxV)
#850: FILE: lib/librte_vhost/vhost_crypto.c:658:
+ rte_hexdump(stdout ,"", dst, to_write);
^
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#915: FILE: lib/librte_vhost/vhost_crypto.c:723:
+ unsigned nb_elts, unsigned cache_size, int socket_id)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#915: FILE: lib/librte_vhost/vhost_crypto.c:723:
+ unsigned nb_elts, unsigned cache_size, int socket_id)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#958: FILE: lib/librte_vhost/vhost_crypto.c:766:
+ snprintf(name, 127, "HASH_VHOST_CRYPT_%u", (unsigned)vid);
ERROR:SPACING: space prohibited before that ',' (ctx:WxV)
#1064: FILE: lib/librte_vhost/vhost_crypto.c:872:
+ rte_hexdump(stdout ,"IV:", iv_data, cipher->para.iv_len);
^
ERROR:SPACING: space required after that ',' (ctx:WxV)
#1064: FILE: lib/librte_vhost/vhost_crypto.c:872:
+ rte_hexdump(stdout ,"IV:", iv_data, cipher->para.iv_len);
^
ERROR:SPACING: space prohibited before that ',' (ctx:WxV)
#1075: FILE: lib/librte_vhost/vhost_crypto.c:883:
+ rte_hexdump(stdout ,"SRC:", vc_req->src_data, cipher->para.src_data_len);
^
ERROR:SPACING: space required after that ',' (ctx:WxV)
#1075: FILE: lib/librte_vhost/vhost_crypto.c:883:
+ rte_hexdump(stdout ,"SRC:", vc_req->src_data, cipher->para.src_data_len);
^
WARNING:TYPO_SPELLING: 'retrive' may be misspelled - perhaps 'retrieve'?
#1256: FILE: lib/librte_vhost/vhost_crypto.c:1064:
+ VC_LOG_ERR("Failed to retrive req");
ERROR:OPEN_BRACE: that open brace { should be on the previous line
#1260: FILE: lib/librte_vhost/vhost_crypto.c:1068:
+ if (unlikely(req->header.opcode != VIRTIO_CRYPTO_CIPHER_ENCRYPT &&
+ req->header.opcode != VIRTIO_CRYPTO_CIPHER_DECRYPT))
+ {
WARNING:TYPO_SPELLING: 'unecessary' may be misspelled - perhaps 'unnecessary'?
#1275: FILE: lib/librte_vhost/vhost_crypto.c:1083:
+ /* one branch to avoid unecessary table lookup */
total: 12 errors, 10 warnings, 1404 lines checked
parent reply other threads:[~2017-11-02 20:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20171102201059.2803-5-roy.fan.zhang@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=20171102201215.BA4931B689@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=roy.fan.zhang@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).