automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw31688 [PATCH 04/12] lib/librte_vhost: add session messsage handler
Date: Mon, 27 Nov 2017 21:03:42 +0100 (CET)	[thread overview]
Message-ID: <20171127200342.98C111B195@dpdk.org> (raw)
In-Reply-To: <20171127200115.31049-5-roy.fan.zhang@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/31688

_coding style issues_


WARNING:TYPO_SPELLING: 'messsage' may be misspelled - perhaps 'message'?
#5: 
Subject: [dpdk-dev] [PATCH 04/12] lib/librte_vhost: add session messsage handler

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#82: FILE: lib/librte_vhost/vhost_crypto.c:54:
+#define INHDR_LEN ^I^I(sizeof(struct virtio_crypto_inhdr))$

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#115: FILE: lib/librte_vhost/vhost_crypto.c:87:
+#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
#119: FILE: lib/librte_vhost/vhost_crypto.c:91:
+#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
#249: FILE: lib/librte_vhost/vhost_crypto.c:221:
+static int
+transform_cipher_param(struct rte_crypto_sym_xform *xform,
+		VhostUserCryptoSessionParam *param) {

ERROR:SPACING: space required before the open parenthesis '('
#337: FILE: lib/librte_vhost/vhost_crypto.c:309:
+	switch(sess_param->op_type) {

total: 3 errors, 3 warnings, 447 lines checked

           reply	other threads:[~2017-11-27 20:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20171127200115.31049-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=20171127200342.98C111B195@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).