From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Junfeng Guo <junfeng.guo@intel.com>
Subject: [dpdk-test-report] |WARNING| pw88069 [PATCH 2/2] net/iavf: support GTPU inner IPv6 for FDIR
Date: Mon, 22 Feb 2021 03:20:35 +0100 (CET) [thread overview]
Message-ID: <20210222022035.E39772C58@dpdk.org> (raw)
In-Reply-To: <20210222100908.4073232-3-junfeng.guo@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/88069
_coding style issues_
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#97: FILE: drivers/net/iavf/iavf_fdir.c:153:
+ {iavf_pattern_eth_ipv4_gtpu_ipv6, IAVF_FDIR_INSET_GTPU_IPV6, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#98: FILE: drivers/net/iavf/iavf_fdir.c:154:
+ {iavf_pattern_eth_ipv4_gtpu_ipv6_udp, IAVF_FDIR_INSET_GTPU_IPV6_UDP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#99: FILE: drivers/net/iavf/iavf_fdir.c:155:
+ {iavf_pattern_eth_ipv4_gtpu_ipv6_tcp, IAVF_FDIR_INSET_GTPU_IPV6_TCP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#104: FILE: drivers/net/iavf/iavf_fdir.c:160:
+ {iavf_pattern_eth_ipv4_gtpu_eh_ipv6, IAVF_FDIR_INSET_GTPU_IPV6, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#105: FILE: drivers/net/iavf/iavf_fdir.c:161:
+ {iavf_pattern_eth_ipv4_gtpu_eh_ipv6_udp,IAVF_FDIR_INSET_GTPU_IPV6_UDP, IAVF_INSET_NONE},
ERROR:SPACING: space required after that ',' (ctx:VxV)
#105: FILE: drivers/net/iavf/iavf_fdir.c:161:
+ {iavf_pattern_eth_ipv4_gtpu_eh_ipv6_udp,IAVF_FDIR_INSET_GTPU_IPV6_UDP, IAVF_INSET_NONE},
^
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#106: FILE: drivers/net/iavf/iavf_fdir.c:162:
+ {iavf_pattern_eth_ipv4_gtpu_eh_ipv6_tcp,IAVF_FDIR_INSET_GTPU_IPV6_TCP, IAVF_INSET_NONE},
ERROR:SPACING: space required after that ',' (ctx:VxV)
#106: FILE: drivers/net/iavf/iavf_fdir.c:162:
+ {iavf_pattern_eth_ipv4_gtpu_eh_ipv6_tcp,IAVF_FDIR_INSET_GTPU_IPV6_TCP, IAVF_INSET_NONE},
^
total: 2 errors, 6 warnings, 0 checks, 62 lines checked
next parent reply other threads:[~2021-02-22 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210222100908.4073232-3-junfeng.guo@intel.com>
2021-02-22 2:20 ` checkpatch [this message]
2021-02-22 4:05 ` [dpdk-test-report] |FAILURE| pw88069 " 0-day Robot
2021-02-22 4:09 ` [dpdk-test-report] |SUCCESS| pw88069 [dpdk-dev] [PATCH 2/2] " 0-day Robot
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=20210222022035.E39772C58@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=junfeng.guo@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).