From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Zhichao Zeng <zhichaox.zeng@intel.com>
Subject: |WARNING| pw135047 [PATCH] net/iavf: support rte flow with mask for FDIR
Date: Tue, 12 Dec 2023 03:25:39 +0100 (CET) [thread overview]
Message-ID: <20231212022539.A2983123D87@dpdk.org> (raw)
In-Reply-To: <20231212023406.820293-1-zhichaox.zeng@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/135047
_coding style issues_
WARNING:LONG_LINE: line length of 102 exceeds 100 columns
#147: FILE: drivers/net/iavf/iavf_fdir.c:878:
+ } else if (!rte_is_zero_ether_addr(ð_mask->hdr.src_addr)) {
WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#163: FILE: drivers/net/iavf/iavf_fdir.c:886:
+ if (eth_mask->hdr.ether_type != RTE_BE16(0xffff)) {
WARNING:LONG_LINE: line length of 104 exceeds 100 columns
#170: FILE: drivers/net/iavf/iavf_fdir.c:893:
+ ether_type = rte_be_to_cpu_16(eth_spec->hdr.ether_type);
WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#171: FILE: drivers/net/iavf/iavf_fdir.c:894:
+ if (ether_type == RTE_ETHER_TYPE_IPV4 ||
WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#503: FILE: drivers/net/iavf/iavf_fdir.c:1201:
+ VIRTCHNL_ADD_PROTO_HDR_FIELD_BIT(hdr, UDP, SRC_PORT);
WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#507: FILE: drivers/net/iavf/iavf_fdir.c:1205:
+ VIRTCHNL_ADD_PROTO_HDR_FIELD_BIT(hdr, UDP, DST_PORT);
WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#589: FILE: drivers/net/iavf/iavf_fdir.c:1265:
+ VIRTCHNL_ADD_PROTO_HDR_FIELD_BIT(hdr, TCP, SRC_PORT);
WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#593: FILE: drivers/net/iavf/iavf_fdir.c:1269:
+ VIRTCHNL_ADD_PROTO_HDR_FIELD_BIT(hdr, TCP, DST_PORT);
total: 0 errors, 8 warnings, 0 checks, 541 lines checked
next prev parent reply other threads:[~2023-12-12 2:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231212023406.820293-1-zhichaox.zeng@intel.com>
2023-12-12 2:11 ` |SUCCESS| " qemudev
2023-12-12 2:15 ` qemudev
2023-12-12 2:25 ` checkpatch [this message]
2023-12-12 3:24 ` 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=20231212022539.A2983123D87@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=zhichaox.zeng@intel.com \
/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).