From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jie Wang <jie1x.wang@intel.com>
Subject: |WARNING| pw114863 [PATCH v2 3/5] net/iavf: support flow subscrption pattern
Date: Fri, 12 Aug 2022 11:07:47 +0200 (CEST) [thread overview]
Message-ID: <20220812090747.09EAD120775@dpdk.org> (raw)
In-Reply-To: <20220812170447.186992-4-jie1x.wang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/114863
_coding style issues_
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#143: FILE: drivers/net/iavf/iavf_fsub.c:61:
+ {iavf_pattern_ethertype, IAVF_SW_INSET_ETHER, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#144: FILE: drivers/net/iavf/iavf_fsub.c:62:
+ {iavf_pattern_eth_ipv4, IAVF_SW_INSET_MAC_IPV4, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#145: FILE: drivers/net/iavf/iavf_fsub.c:63:
+ {iavf_pattern_eth_vlan_ipv4, IAVF_SW_INSET_MAC_VLAN_IPV4, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#146: FILE: drivers/net/iavf/iavf_fsub.c:64:
+ {iavf_pattern_eth_ipv4_udp, IAVF_SW_INSET_MAC_IPV4_UDP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#147: FILE: drivers/net/iavf/iavf_fsub.c:65:
+ {iavf_pattern_eth_ipv4_tcp, IAVF_SW_INSET_MAC_IPV4_TCP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#148: FILE: drivers/net/iavf/iavf_fsub.c:66:
+ {iavf_pattern_eth_ipv6, IAVF_SW_INSET_MAC_IPV6, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#149: FILE: drivers/net/iavf/iavf_fsub.c:67:
+ {iavf_pattern_eth_ipv6_udp, IAVF_SW_INSET_MAC_IPV6_UDP, IAVF_INSET_NONE},
WARNING:LONG_LINE: line length of 113 exceeds 100 columns
#150: FILE: drivers/net/iavf/iavf_fsub.c:68:
+ {iavf_pattern_eth_ipv6_tcp, IAVF_SW_INSET_MAC_IPV6_TCP, IAVF_INSET_NONE},
total: 0 errors, 8 warnings, 0 checks, 629 lines checked
parent reply other threads:[~2022-08-12 9:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220812170447.186992-4-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=20220812090747.09EAD120775@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).