From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Simei Su <simei.su@intel.com>
Subject: [dpdk-test-report] |WARNING| pw67654 [PATCH v2 3/5] net/iavf: add support for FDIR L2TPv3 and IPSec
Date: Thu, 2 Apr 2020 15:35:49 +0200 (CEST) [thread overview]
Message-ID: <20200402133549.4A0071BF4F@dpdk.org> (raw)
In-Reply-To: <1585834375-157346-4-git-send-email-simei.su@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/67654
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#103: FILE: drivers/net/iavf/iavf_fdir.c:107:
+ {iavf_pattern_eth_ipv4_l2tpv3, IAVF_FDIR_INSET_L2TPV3OIP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#104: FILE: drivers/net/iavf/iavf_fdir.c:108:
+ {iavf_pattern_eth_ipv6_l2tpv3, IAVF_FDIR_INSET_L2TPV3OIP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#105: FILE: drivers/net/iavf/iavf_fdir.c:109:
+ {iavf_pattern_eth_ipv4_esp, IAVF_FDIR_INSET_ESP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#106: FILE: drivers/net/iavf/iavf_fdir.c:110:
+ {iavf_pattern_eth_ipv6_esp, IAVF_FDIR_INSET_ESP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#107: FILE: drivers/net/iavf/iavf_fdir.c:111:
+ {iavf_pattern_eth_ipv4_ah, IAVF_FDIR_INSET_AH, IAVF_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#108: FILE: drivers/net/iavf/iavf_fdir.c:112:
+ {iavf_pattern_eth_ipv6_ah, IAVF_FDIR_INSET_AH, IAVF_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#109: FILE: drivers/net/iavf/iavf_fdir.c:113:
+ {iavf_pattern_eth_ipv4_udp_esp, IAVF_FDIR_INSET_IPV4_NATT_ESP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#110: FILE: drivers/net/iavf/iavf_fdir.c:114:
+ {iavf_pattern_eth_ipv6_udp_esp, IAVF_FDIR_INSET_IPV6_NATT_ESP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line over 90 characters
#139: FILE: drivers/net/iavf/iavf_fdir.c:771:
+ VIRTCHNL_ADD_PROTO_HDR_FIELD_BIT(hdr, L2TPV3, SESS_ID);
total: 0 errors, 9 warnings, 0 checks, 115 lines checked
parent reply other threads:[~2020-04-02 13:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1585834375-157346-4-git-send-email-simei.su@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=20200402133549.4A0071BF4F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=simei.su@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).