From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Li Zhang <lizh@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw79612 [PATCH v5 1/1] net/mlx5: support match ICMP identifier fields
Date: Mon, 5 Oct 2020 11:20:08 +0200 (CEST) [thread overview]
Message-ID: <20201005092008.C4E6237B7@dpdk.org> (raw)
In-Reply-To: <20201005091816.9002-1-lizh@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/79612
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#152: FILE: drivers/net/mlx5/mlx5_flow_dv.c:7423:
+^I^I ^I icmp_header_data_m);$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#152: FILE: drivers/net/mlx5/mlx5_flow_dv.c:7423:
+^I^I ^I icmp_header_data_m);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#154: FILE: drivers/net/mlx5/mlx5_flow_dv.c:7425:
+^I^I ^I icmp_header_data_v & icmp_header_data_m);$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#154: FILE: drivers/net/mlx5/mlx5_flow_dv.c:7425:
+^I^I ^I icmp_header_data_v & icmp_header_data_m);$
total: 2 errors, 2 warnings, 0 checks, 72 lines checked
next parent reply other threads:[~2020-10-05 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201005091816.9002-1-lizh@nvidia.com>
2020-10-05 9:20 ` checkpatch [this message]
2020-10-05 10:55 ` [dpdk-test-report] |SUCCESS| pw79612 " 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=20201005092008.C4E6237B7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=lizh@nvidia.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).