From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Subject: [dpdk-test-report] |WARNING| pw29695 [PATCH v2 04/30] net/mlx5: prefix Tx structures and functions
Date: Thu, 5 Oct 2017 14:51:59 +0200 (CEST) [thread overview]
Message-ID: <20171005125159.AF92F1B26B@dpdk.org> (raw)
In-Reply-To: <64deeb917c0976016a5141ea763b3f07efc24a66.1507207731.git.nelio.laranjeiro@6wind.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/29695
_coding style issues_
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct mlx5_txq_ctrl *' should also have an identifier name
#249: FILE: drivers/net/mlx5/mlx5_rxtx.h:308:
+void mlx5_txq_cleanup(struct mlx5_txq_ctrl *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct rte_eth_dev *' should also have an identifier name
#250: FILE: drivers/net/mlx5/mlx5_rxtx.h:309:
+int mlx5_txq_ctrl_setup(struct rte_eth_dev *, struct mlx5_txq_ctrl *, uint16_t,
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct mlx5_txq_ctrl *' should also have an identifier name
#250: FILE: drivers/net/mlx5/mlx5_rxtx.h:309:
+int mlx5_txq_ctrl_setup(struct rte_eth_dev *, struct mlx5_txq_ctrl *, uint16_t,
WARNING:FUNCTION_ARGUMENTS: function definition argument 'uint16_t' should also have an identifier name
#250: FILE: drivers/net/mlx5/mlx5_rxtx.h:309:
+int mlx5_txq_ctrl_setup(struct rte_eth_dev *, struct mlx5_txq_ctrl *, uint16_t,
WARNING:FUNCTION_ARGUMENTS: function definition argument 'unsigned int' should also have an identifier name
#250: FILE: drivers/net/mlx5/mlx5_rxtx.h:309:
+int mlx5_txq_ctrl_setup(struct rte_eth_dev *, struct mlx5_txq_ctrl *, uint16_t,
WARNING:FUNCTION_ARGUMENTS: function definition argument 'const struct rte_eth_txconf *' should also have an identifier name
#250: FILE: drivers/net/mlx5/mlx5_rxtx.h:309:
+int mlx5_txq_ctrl_setup(struct rte_eth_dev *, struct mlx5_txq_ctrl *, uint16_t,
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct rte_mempool *' should also have an identifier name
#261: FILE: drivers/net/mlx5/mlx5_rxtx.h:343:
+void mlx5_txq_mp2mr_iter(struct rte_mempool *, void *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'void *' should also have an identifier name
#261: FILE: drivers/net/mlx5/mlx5_rxtx.h:343:
+void mlx5_txq_mp2mr_iter(struct rte_mempool *, void *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct mlx5_txq_data *' should also have an identifier name
#262: FILE: drivers/net/mlx5/mlx5_rxtx.h:344:
+uint32_t mlx5_txq_mp2mr_reg(struct mlx5_txq_data *, struct rte_mempool *,
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct rte_mempool *' should also have an identifier name
#262: FILE: drivers/net/mlx5/mlx5_rxtx.h:344:
+uint32_t mlx5_txq_mp2mr_reg(struct mlx5_txq_data *, struct rte_mempool *,
WARNING:FUNCTION_ARGUMENTS: function definition argument 'unsigned int' should also have an identifier name
#262: FILE: drivers/net/mlx5/mlx5_rxtx.h:344:
+uint32_t mlx5_txq_mp2mr_reg(struct mlx5_txq_data *, struct rte_mempool *,
total: 0 errors, 11 warnings, 0 checks, 442 lines checked
parent reply other threads:[~2017-10-05 12:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <64deeb917c0976016a5141ea763b3f07efc24a66.1507207731.git.nelio.laranjeiro@6wind.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=20171005125159.AF92F1B26B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nelio.laranjeiro@6wind.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).