From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yahui Cao <yahui.cao@intel.com>
Subject: [dpdk-test-report] |WARNING| pw60126 [PATCH v5 3/9] net/ice: add FDIR create and destroy
Date: Mon, 30 Sep 2019 06:02:38 +0200 (CEST) [thread overview]
Message-ID: <20190930040238.BCAB31B9BF@dpdk.org> (raw)
In-Reply-To: <20190930114547.74803-4-yahui.cao@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/60126
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#111: FILE: drivers/net/ice/ice_fdir_filter.c:47:
+ {pattern_eth_ipv4, ICE_FDIR_INSET_ETH_IPV4, ICE_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#112: FILE: drivers/net/ice/ice_fdir_filter.c:48:
+ {pattern_eth_ipv4_udp, ICE_FDIR_INSET_ETH_IPV4_UDP, ICE_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#113: FILE: drivers/net/ice/ice_fdir_filter.c:49:
+ {pattern_eth_ipv4_tcp, ICE_FDIR_INSET_ETH_IPV4_TCP, ICE_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#114: FILE: drivers/net/ice/ice_fdir_filter.c:50:
+ {pattern_eth_ipv4_sctp, ICE_FDIR_INSET_ETH_IPV4_SCTP, ICE_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#115: FILE: drivers/net/ice/ice_fdir_filter.c:51:
+ {pattern_eth_ipv6, ICE_FDIR_INSET_ETH_IPV6, ICE_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#116: FILE: drivers/net/ice/ice_fdir_filter.c:52:
+ {pattern_eth_ipv6_udp, ICE_FDIR_INSET_ETH_IPV6_UDP, ICE_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#117: FILE: drivers/net/ice/ice_fdir_filter.c:53:
+ {pattern_eth_ipv6_tcp, ICE_FDIR_INSET_ETH_IPV6_TCP, ICE_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#118: FILE: drivers/net/ice/ice_fdir_filter.c:54:
+ {pattern_eth_ipv6_sctp, ICE_FDIR_INSET_ETH_IPV6_SCTP, ICE_INSET_NONE},
total: 0 errors, 8 warnings, 0 checks, 644 lines checked
parent reply other threads:[~2019-09-30 4:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190930114547.74803-4-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=20190930040238.BCAB31B9BF@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).