automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yahui Cao <yahui.cao@intel.com>
Subject: [dpdk-test-report] |WARNING| pw61456 [PATCH v7 9/9] net/ice: add FDIR GTPU tunnel support
Date: Fri, 18 Oct 2019 05:35:24 +0200 (CEST)	[thread overview]
Message-ID: <20191018033524.0EE891E540@dpdk.org> (raw)
In-Reply-To: <20191018111602.26742-10-yahui.cao@intel.com>

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

_coding style issues_


WARNING:LONG_LINE: line over 90 characters
#73: FILE: drivers/net/ice/ice_fdir_filter.c:78:
+	{pattern_eth_ipv4,             ICE_FDIR_INSET_ETH_IPV4,              ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#74: FILE: drivers/net/ice/ice_fdir_filter.c:79:
+	{pattern_eth_ipv4_udp,         ICE_FDIR_INSET_ETH_IPV4_UDP,          ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#75: FILE: drivers/net/ice/ice_fdir_filter.c:80:
+	{pattern_eth_ipv4_tcp,         ICE_FDIR_INSET_ETH_IPV4_TCP,          ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#76: FILE: drivers/net/ice/ice_fdir_filter.c:81:
+	{pattern_eth_ipv4_sctp,        ICE_FDIR_INSET_ETH_IPV4_SCTP,         ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#77: FILE: drivers/net/ice/ice_fdir_filter.c:82:
+	{pattern_eth_ipv6,             ICE_FDIR_INSET_ETH_IPV6,              ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#78: FILE: drivers/net/ice/ice_fdir_filter.c:83:
+	{pattern_eth_ipv6_udp,         ICE_FDIR_INSET_ETH_IPV6_UDP,          ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#79: FILE: drivers/net/ice/ice_fdir_filter.c:84:
+	{pattern_eth_ipv6_tcp,         ICE_FDIR_INSET_ETH_IPV6_TCP,          ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#80: FILE: drivers/net/ice/ice_fdir_filter.c:85:
+	{pattern_eth_ipv6_sctp,        ICE_FDIR_INSET_ETH_IPV6_SCTP,         ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#82: FILE: drivers/net/ice/ice_fdir_filter.c:87:
+				       ICE_FDIR_INSET_VXLAN_IPV4,            ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#84: FILE: drivers/net/ice/ice_fdir_filter.c:89:
+				       ICE_FDIR_INSET_VXLAN_IPV4_UDP,        ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#86: FILE: drivers/net/ice/ice_fdir_filter.c:91:
+				       ICE_FDIR_INSET_VXLAN_IPV4_TCP,        ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#88: FILE: drivers/net/ice/ice_fdir_filter.c:93:
+				       ICE_FDIR_INSET_VXLAN_IPV4_SCTP,       ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#90: FILE: drivers/net/ice/ice_fdir_filter.c:95:
+				       ICE_FDIR_INSET_VXLAN_IPV4,            ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#92: FILE: drivers/net/ice/ice_fdir_filter.c:97:
+				       ICE_FDIR_INSET_VXLAN_IPV4_UDP,        ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#94: FILE: drivers/net/ice/ice_fdir_filter.c:99:
+				       ICE_FDIR_INSET_VXLAN_IPV4_TCP,        ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#96: FILE: drivers/net/ice/ice_fdir_filter.c:101:
+				       ICE_FDIR_INSET_VXLAN_IPV4_SCTP,       ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#107: FILE: drivers/net/ice/ice_fdir_filter.c:129:
+	{pattern_eth_ipv4_gtpu_ipv4,   ICE_FDIR_INSET_GTPU_IPV4,             ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#109: FILE: drivers/net/ice/ice_fdir_filter.c:131:
+				       ICE_FDIR_INSET_GTPU_IPV4,             ICE_INSET_NONE},

WARNING:LONG_LINE: line over 90 characters
#111: FILE: drivers/net/ice/ice_fdir_filter.c:133:
+				       ICE_FDIR_INSET_GTPU_IPV4,             ICE_INSET_NONE},

total: 0 errors, 19 warnings, 0 checks, 261 lines checked

           reply	other threads:[~2019-10-18  3:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20191018111602.26742-10-yahui.cao@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=20191018033524.0EE891E540@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=yahui.cao@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).