automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Zhirun Yan <zhirun.yan@intel.com>
Subject: [dpdk-test-report] |WARNING| pw85589 [PATCH v1 5/5] net/ice: enable FDIR outer/inner fields for VXLAN
Date: Mon, 21 Dec 2020 07:59:18 +0100 (CET)	[thread overview]
Message-ID: <20201221065918.CA43ECBDF@dpdk.org> (raw)
In-Reply-To: <20201221065150.1600719-6-zhirun.yan@intel.com>

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

_coding style issues_


WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#97: FILE: drivers/net/ice/ice_fdir_filter.c:101:
+	{pattern_eth_ipv4_udp_vxlan_ipv4,		ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_L,		ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#98: FILE: drivers/net/ice/ice_fdir_filter.c:102:
+	{pattern_eth_ipv4_udp_vxlan_ipv4_udp,		ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_UDP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#99: FILE: drivers/net/ice/ice_fdir_filter.c:103:
+	{pattern_eth_ipv4_udp_vxlan_ipv4_tcp,		ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_TCP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#100: FILE: drivers/net/ice/ice_fdir_filter.c:104:
+	{pattern_eth_ipv4_udp_vxlan_ipv4_sctp,		ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_SCTP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#101: FILE: drivers/net/ice/ice_fdir_filter.c:105:
+	{pattern_eth_ipv4_udp_vxlan_eth_ipv4,		ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_L,		ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#102: FILE: drivers/net/ice/ice_fdir_filter.c:106:
+	{pattern_eth_ipv4_udp_vxlan_eth_ipv4_udp,	ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_UDP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#103: FILE: drivers/net/ice/ice_fdir_filter.c:107:
+	{pattern_eth_ipv4_udp_vxlan_eth_ipv4_tcp,	ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_TCP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#104: FILE: drivers/net/ice/ice_fdir_filter.c:108:
+	{pattern_eth_ipv4_udp_vxlan_eth_ipv4_sctp,	ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_SCTP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#120: FILE: drivers/net/ice/ice_fdir_filter.c:119:
+	{pattern_eth_ipv4_udp_vxlan_ipv4,		ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_L,		ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#121: FILE: drivers/net/ice/ice_fdir_filter.c:120:
+	{pattern_eth_ipv4_udp_vxlan_ipv4_udp,		ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_UDP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#122: FILE: drivers/net/ice/ice_fdir_filter.c:121:
+	{pattern_eth_ipv4_udp_vxlan_ipv4_tcp,		ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_TCP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#123: FILE: drivers/net/ice/ice_fdir_filter.c:122:
+	{pattern_eth_ipv4_udp_vxlan_ipv4_sctp,		ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_SCTP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#124: FILE: drivers/net/ice/ice_fdir_filter.c:123:
+	{pattern_eth_ipv4_udp_vxlan_eth_ipv4,		ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_L,		ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#125: FILE: drivers/net/ice/ice_fdir_filter.c:124:
+	{pattern_eth_ipv4_udp_vxlan_eth_ipv4_udp,	ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_UDP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#126: FILE: drivers/net/ice/ice_fdir_filter.c:125:
+	{pattern_eth_ipv4_udp_vxlan_eth_ipv4_tcp,	ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_TCP_L,	ICE_INSET_NONE},

WARNING:LONG_LINE: line length of 144 exceeds 100 columns
#127: FILE: drivers/net/ice/ice_fdir_filter.c:126:
+	{pattern_eth_ipv4_udp_vxlan_eth_ipv4_sctp,	ICE_FDIR_INSET_VXLAN_IPV4_F,	ICE_FDIR_INSET_VXLAN_IPV4_SCTP_L,	ICE_INSET_NONE},

total: 0 errors, 16 warnings, 0 checks, 56 lines checked

           reply	other threads:[~2020-12-21  6:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20201221065150.1600719-6-zhirun.yan@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=20201221065918.CA43ECBDF@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=zhirun.yan@intel.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).