From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jie Wang <jie1x.wang@intel.com>
Subject: |WARNING| pw107357 [PATCH v3 2/2] net/iavf: support L2TPv2 for AVF FDIR
Date: Fri, 11 Feb 2022 09:09:57 +0100 (CET) [thread overview]
Message-ID: <20220211080957.39BF5120715@dpdk.org> (raw)
In-Reply-To: <20220211080929.424165-3-jie1x.wang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/107357
_coding style issues_
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#142: FILE: drivers/net/iavf/iavf_fdir.c:304:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2, IAVF_FDIR_INSET_L2TPV2, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#143: FILE: drivers/net/iavf/iavf_fdir.c:305:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp, IAVF_FDIR_INSET_L2TPV2, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#144: FILE: drivers/net/iavf/iavf_fdir.c:306:
+ {iavf_pattern_eth_ipv6_udp_l2tpv2, IAVF_FDIR_INSET_L2TPV2, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#145: FILE: drivers/net/iavf/iavf_fdir.c:307:
+ {iavf_pattern_eth_ipv6_udp_l2tpv2_ppp, IAVF_FDIR_INSET_L2TPV2, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#146: FILE: drivers/net/iavf/iavf_fdir.c:308:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv4, IAVF_FDIR_INSET_L2TPV2_PPP_IPV4, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#147: FILE: drivers/net/iavf/iavf_fdir.c:309:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv4_udp, IAVF_FDIR_INSET_L2TPV2_PPP_IPV4_UDP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#148: FILE: drivers/net/iavf/iavf_fdir.c:310:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv4_tcp, IAVF_FDIR_INSET_L2TPV2_PPP_IPV4_TCP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#149: FILE: drivers/net/iavf/iavf_fdir.c:311:
+ {iavf_pattern_eth_ipv6_udp_l2tpv2_ppp_ipv4, IAVF_FDIR_INSET_L2TPV2_PPP_IPV4, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#150: FILE: drivers/net/iavf/iavf_fdir.c:312:
+ {iavf_pattern_eth_ipv6_udp_l2tpv2_ppp_ipv4_udp, IAVF_FDIR_INSET_L2TPV2_PPP_IPV4_UDP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#151: FILE: drivers/net/iavf/iavf_fdir.c:313:
+ {iavf_pattern_eth_ipv6_udp_l2tpv2_ppp_ipv4_tcp, IAVF_FDIR_INSET_L2TPV2_PPP_IPV4_TCP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#152: FILE: drivers/net/iavf/iavf_fdir.c:314:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv6, IAVF_FDIR_INSET_L2TPV2_PPP_IPV6, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#153: FILE: drivers/net/iavf/iavf_fdir.c:315:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv6_udp, IAVF_FDIR_INSET_L2TPV2_PPP_IPV6_UDP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#154: FILE: drivers/net/iavf/iavf_fdir.c:316:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv6_tcp, IAVF_FDIR_INSET_L2TPV2_PPP_IPV6_TCP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#155: FILE: drivers/net/iavf/iavf_fdir.c:317:
+ {iavf_pattern_eth_ipv6_udp_l2tpv2_ppp_ipv6, IAVF_FDIR_INSET_L2TPV2_PPP_IPV6, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#156: FILE: drivers/net/iavf/iavf_fdir.c:318:
+ {iavf_pattern_eth_ipv6_udp_l2tpv2_ppp_ipv6_udp, IAVF_FDIR_INSET_L2TPV2_PPP_IPV6_UDP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#157: FILE: drivers/net/iavf/iavf_fdir.c:319:
+ {iavf_pattern_eth_ipv6_udp_l2tpv2_ppp_ipv6_tcp, IAVF_FDIR_INSET_L2TPV2_PPP_IPV6_TCP, IAVF_INSET_NONE},
total: 0 errors, 16 warnings, 0 checks, 241 lines checked
next parent reply other threads:[~2022-02-11 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220211080929.424165-3-jie1x.wang@intel.com>
2022-02-11 8:09 ` checkpatch [this message]
2022-02-11 9:39 ` |FAILURE| " 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=20220211080957.39BF5120715@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jie1x.wang@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).