From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jie Wang <jie1x.wang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw99540 [PATCH 1/4] net/iavf: support PPPoL2TPv2oUDP over IPv4 RSS Hash
Date: Fri, 24 Sep 2021 09:21:23 +0200 (CEST) [thread overview]
Message-ID: <20210924072123.E525012075A@dpdk.org> (raw)
In-Reply-To: <20210924151705.287571-2-jie1x.wang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/99540
_coding style issues_
WARNING:LONG_LINE: line length of 116 exceeds 100 columns
#249: FILE: drivers/net/iavf/iavf_hash.c:543:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv4, IAVF_RSS_TYPE_INNER_IPV4, &udp_l2tpv2_ppp_ipv4_tmplt},
WARNING:LONG_LINE: line length of 120 exceeds 100 columns
#250: FILE: drivers/net/iavf/iavf_hash.c:544:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv4_udp, IAVF_RSS_TYPE_INNER_IPV4_UDP, &udp_l2tpv2_ppp_ipv4_udp_tmplt},
WARNING:LONG_LINE: line length of 120 exceeds 100 columns
#251: FILE: drivers/net/iavf/iavf_hash.c:545:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv4_tcp, IAVF_RSS_TYPE_INNER_IPV4_TCP, &udp_l2tpv2_ppp_ipv4_tcp_tmplt},
WARNING:LONG_LINE: line length of 116 exceeds 100 columns
#260: FILE: drivers/net/iavf/iavf_hash.c:607:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv6, IAVF_RSS_TYPE_INNER_IPV6, &udp_l2tpv2_ppp_ipv6_tmplt},
WARNING:LONG_LINE: line length of 120 exceeds 100 columns
#261: FILE: drivers/net/iavf/iavf_hash.c:608:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv6_udp, IAVF_RSS_TYPE_INNER_IPV6_UDP, &udp_l2tpv2_ppp_ipv6_udp_tmplt},
WARNING:LONG_LINE: line length of 120 exceeds 100 columns
#262: FILE: drivers/net/iavf/iavf_hash.c:609:
+ {iavf_pattern_eth_ipv4_udp_l2tpv2_ppp_ipv6_tcp, IAVF_RSS_TYPE_INNER_IPV6_TCP, &udp_l2tpv2_ppp_ipv6_tcp_tmplt},
total: 0 errors, 6 warnings, 0 checks, 249 lines checked
parent reply other threads:[~2021-09-24 7:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210924151705.287571-2-jie1x.wang@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=20210924072123.E525012075A@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).