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| pw60131 [PATCH v5 8/9] net/ice: add FDIR vxlan tunnel support
Date: Mon, 30 Sep 2019 06:02:44 +0200 (CEST)	[thread overview]
Message-ID: <20190930040244.CEDE47CBC@dpdk.org> (raw)
In-Reply-To: <20190930114547.74803-9-yahui.cao@intel.com>

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

_coding style issues_


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

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

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

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

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

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

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

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

total: 0 errors, 8 warnings, 0 checks, 258 lines checked

           reply	other threads:[~2019-09-30  4:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20190930114547.74803-9-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=20190930040244.CEDE47CBC@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).