From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Asaf Penso <asafp@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw69832 [PATCH v3] net/mlx5: add 200G link speed
Date: Wed, 6 May 2020 14:23:25 +0200 (CEST) [thread overview]
Message-ID: <20200506122325.2DC1E1D6D0@dpdk.org> (raw)
In-Reply-To: <1588767728-5722-1-git-send-email-asafp@mellanox.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/69832
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <ETHTOOL_LINK_MODE_200000baseKR4_Full_BIT>
#232: FILE: drivers/net/mlx5/mlx5_ethdev.c:124:
+#define ETHTOOL_LINK_MODE_200000baseKR4_Full_BIT 62
CHECK:CAMELCASE: Avoid CamelCase: <ETHTOOL_LINK_MODE_200000baseSR4_Full_BIT>
#233: FILE: drivers/net/mlx5/mlx5_ethdev.c:125:
+#define ETHTOOL_LINK_MODE_200000baseSR4_Full_BIT 63
CHECK:CAMELCASE: Avoid CamelCase: <ETHTOOL_LINK_MODE_200000baseLR4_ER4_FR4_Full_BIT>
#234: FILE: drivers/net/mlx5/mlx5_ethdev.c:126:
+#define ETHTOOL_LINK_MODE_200000baseLR4_ER4_FR4_Full_BIT 0 /* 64 - 64 */
CHECK:CAMELCASE: Avoid CamelCase: <ETHTOOL_LINK_MODE_200000baseDR4_Full_BIT>
#235: FILE: drivers/net/mlx5/mlx5_ethdev.c:127:
+#define ETHTOOL_LINK_MODE_200000baseDR4_Full_BIT 1 /* 65 - 64 */
CHECK:CAMELCASE: Avoid CamelCase: <ETHTOOL_LINK_MODE_200000baseCR4_Full_BIT>
#236: FILE: drivers/net/mlx5/mlx5_ethdev.c:128:
+#define ETHTOOL_LINK_MODE_200000baseCR4_Full_BIT 2 /* 66 - 64 */
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#262: FILE: drivers/net/mlx5/mlx5_ethdev.c:1047:
+ MLX5_BITSHIFT(
total: 0 errors, 0 warnings, 132 lines checked
next parent reply other threads:[~2020-05-06 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1588767728-5722-1-git-send-email-asafp@mellanox.com>
2020-05-06 12:23 ` checkpatch [this message]
2020-05-06 19:13 ` [dpdk-test-report] |WARNING| pw69832 " 0-day Robot
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=20200506122325.2DC1E1D6D0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=asafp@mellanox.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).