From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-test-report] |WARNING| pw102611 [PATCH v6] ethdev: add namespace
Date: Fri, 22 Oct 2021 04:06:00 +0200 (CEST) [thread overview]
Message-ID: <20211022020600.ACE9B121E15@dpdk.org> (raw)
In-Reply-To: <20211022020243.2932559-1-ferruh.yigit@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/102611
_coding style issues_
WARNING:LONG_LINE: line length of 102 exceeds 100 columns
#1173: FILE: app/test-pmd/cmdline.c:7515:
+ {RTE_ETH_FC_NONE, RTE_ETH_FC_TX_PAUSE}, {RTE_ETH_FC_RX_PAUSE, RTE_ETH_FC_FULL}
ERROR:SWITCH_CASE_INDENT_LEVEL: switch and case should be at the same indent
#8724: FILE: drivers/net/e1000/igb_rxtx.c:2284:
switch (dev->data->dev_conf.rxmode.mq_mode) {
+ case RTE_ETH_MQ_RX_RSS:
[...]
+ case RTE_ETH_MQ_RX_VMDQ_ONLY:
[...]
+ case RTE_ETH_MQ_RX_NONE:
WARNING:LONG_LINE: line length of 119 exceeds 100 columns
#14016: FILE: drivers/net/iavf/iavf_hash.c:499:
+ {iavf_pattern_eth_ipv4_gtpu, RTE_ETH_RSS_IPV4, &outer_ipv4_udp_tmplt},
WARNING:LONG_LINE: line length of 118 exceeds 100 columns
#14027: FILE: drivers/net/iavf/iavf_hash.c:541:
+ {iavf_pattern_eth_ipv4_gtpc, RTE_ETH_RSS_IPV4, &ipv4_udp_gtpc_tmplt},
WARNING:LONG_LINE: line length of 114 exceeds 100 columns
#14028: FILE: drivers/net/iavf/iavf_hash.c:542:
+ {iavf_pattern_eth_ecpri, RTE_ETH_RSS_ECPRI, ð_ecpri_tmplt},
WARNING:LONG_LINE: line length of 115 exceeds 100 columns
#14029: FILE: drivers/net/iavf/iavf_hash.c:543:
+ {iavf_pattern_eth_ipv4_ecpri, RTE_ETH_RSS_ECPRI, &ipv4_ecpri_tmplt},
WARNING:LONG_LINE: line length of 119 exceeds 100 columns
#14038: FILE: drivers/net/iavf/iavf_hash.c:568:
+ {iavf_pattern_eth_ipv6_gtpu, RTE_ETH_RSS_IPV6, &outer_ipv6_udp_tmplt},
WARNING:LONG_LINE: line length of 118 exceeds 100 columns
#14047: FILE: drivers/net/iavf/iavf_hash.c:610:
+ {iavf_pattern_eth_ipv6_gtpc, RTE_ETH_RSS_IPV6, &ipv6_udp_gtpc_tmplt},
ERROR:SPACING: space prohibited after that '*' (ctx:ExW)
#19021: FILE: drivers/net/ixgbe/rte_pmd_ixgbe.h:289:
+* RTE_ETH_VMDQ_ACCEPT_BROADCAST and RTE_ETH_VMDQ_ACCEPT_MULTICAST will be used
^
WARNING:BLOCK_COMMENT_STYLE: Block comments use * on subsequent lines
#31333: FILE: lib/ethdev/rte_ethdev.h:1531:
+ uint32_t link_speeds; /**< bitmap of RTE_ETH_LINK_SPEED_XXX of speeds to be
+ used. RTE_ETH_LINK_SPEED_FIXED disables link
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#31347: FILE: lib/ethdev/rte_ethdev.h:1562:
+ is needed,and the variable must be set RTE_ETH_DCB_PFC_SUPPORT. */
total: 2 errors, 9 warnings, 28212 lines checked
next parent reply other threads:[~2021-10-22 2:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211022020243.2932559-1-ferruh.yigit@intel.com>
2021-10-22 2:06 ` checkpatch [this message]
2021-10-22 2:28 [dpdk-test-report] |WARNING| pw102611 [PATCH] [v6] " dpdklab
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=20211022020600.ACE9B121E15@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ferruh.yigit@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).