From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jeff Guo <jia.guo@intel.com>
Subject: [dpdk-test-report] |WARNING| pw91213 [PATCH v4 4/4] net/iavf: support FDIR for IP fragment packet
Date: Tue, 13 Apr 2021 10:17:22 +0200 (CEST) [thread overview]
Message-ID: <20210413081722.0326B1209EC@dpdk.org> (raw)
In-Reply-To: <20210413081032.60509-5-jia.guo@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/91213
_coding style issues_
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#99: FILE: drivers/net/iavf/iavf_fdir.c:149:
+ {iavf_pattern_eth_ipv6_frag_ext, IAVF_FDIR_INSET_ETH_IPV6_FRAG_EXT, IAVF_INSET_NONE},
total: 0 errors, 1 warnings, 0 checks, 635 lines checked
next parent reply other threads:[~2021-04-13 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210413081032.60509-5-jia.guo@intel.com>
2021-04-13 8:17 ` checkpatch [this message]
2021-04-13 9:55 ` [dpdk-test-report] |FAILURE| pw91213 " 0-day Robot
2021-04-13 9:57 ` [dpdk-test-report] |FAILURE| pw91213 [dpdk-dev] [PATCH v4 4/4] " 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=20210413081722.0326B1209EC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jia.guo@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).