automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yongseok Koh <yskoh@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw24804 [PATCH] net/mlx5: add vectorized Rx
Date: Sun, 28 May 2017 17:41:22 +0200 (CEST)	[thread overview]
Message-ID: <20170528154122.B841A58EC@dpdk.org> (raw)
In-Reply-To: <20170528154035.32198-1-yskoh@mellanox.com>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#155: FILE: drivers/net/mlx5/mlx5_rxq.c:1224:
+^I^I^I^I^I        sizeof(struct rte_mbuf *),$

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#184: FILE: drivers/net/mlx5/mlx5_rxtx.c:1952:
+#if !defined (RTE_ARCH_X86_64)

WARNING:TYPO_SPELLING: 'vaild' may be misspelled - perhaps 'valid'?
#505: FILE: drivers/net/mlx5/mlx5_rxtx.c:2273:
+	 * E. get vaild CQEs.

WARNING:FUNCTION_ARGUMENTS: function definition argument 'void *' should also have an identifier name
#701: FILE: drivers/net/mlx5/mlx5_rxtx.h:339:
+uint16_t mlx5_rx_burst_vec(void *, struct rte_mbuf **, uint16_t);

WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct rte_mbuf **' should also have an identifier name
#701: FILE: drivers/net/mlx5/mlx5_rxtx.h:339:
+uint16_t mlx5_rx_burst_vec(void *, struct rte_mbuf **, uint16_t);

WARNING:FUNCTION_ARGUMENTS: function definition argument 'uint16_t' should also have an identifier name
#701: FILE: drivers/net/mlx5/mlx5_rxtx.h:339:
+uint16_t mlx5_rx_burst_vec(void *, struct rte_mbuf **, uint16_t);

total: 1 errors, 5 warnings, 0 checks, 640 lines checked

           reply	other threads:[~2017-05-28 15:41 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20170528154035.32198-1-yskoh@mellanox.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=20170528154122.B841A58EC@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=yskoh@mellanox.com \
    /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).