From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Mohsin Kazmi <mohsin.kazmi14@gmail.com>
Subject: [dpdk-test-report] |WARNING| pw94800 [PATCH] net: prepare the outer ipv4 hdr for checksum
Date: Thu, 24 Jun 2021 17:17:46 +0200 (CEST) [thread overview]
Message-ID: <20210624151746.7821E122E3A@dpdk.org> (raw)
In-Reply-To: <20210624151449.39799-1-mohsin.kazmi14@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/94800
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#98: FILE: lib/net/rte_net.h:133:
+ /*$
ERROR:CODE_INDENT: code indent should use tabs where possible
#99: FILE: lib/net/rte_net.h:134:
+ * prepare outer ipv4 header checksum by setting it to 0,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#100: FILE: lib/net/rte_net.h:135:
+ * in order to be computed by hardware NICs.$
ERROR:CODE_INDENT: code indent should use tabs where possible
#101: FILE: lib/net/rte_net.h:136:
+ */$
ERROR:CODE_INDENT: code indent should use tabs where possible
#102: FILE: lib/net/rte_net.h:137:
+ if (ol_flags & PKT_TX_OUTER_IP_CKSUM) {$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#102: FILE: lib/net/rte_net.h:137:
+ if (ol_flags & PKT_TX_OUTER_IP_CKSUM) {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#103: FILE: lib/net/rte_net.h:138:
+ ipv4_hdr = rte_pktmbuf_mtod_offset(m, struct rte_ipv4_hdr *,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#103: FILE: lib/net/rte_net.h:138:
+ ipv4_hdr = rte_pktmbuf_mtod_offset(m, struct rte_ipv4_hdr *,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#104: FILE: lib/net/rte_net.h:139:
+ m->outer_l2_len);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#104: FILE: lib/net/rte_net.h:139:
+ m->outer_l2_len);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#105: FILE: lib/net/rte_net.h:140:
+ ipv4_hdr->hdr_checksum = 0;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#105: FILE: lib/net/rte_net.h:140:
+ ipv4_hdr->hdr_checksum = 0;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#106: FILE: lib/net/rte_net.h:141:
+ }$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#106: FILE: lib/net/rte_net.h:141:
+ }$
ERROR:CODE_INDENT: code indent should use tabs where possible
#107: FILE: lib/net/rte_net.h:142:
+ }$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#107: FILE: lib/net/rte_net.h:142:
+ }$
total: 10 errors, 6 warnings, 19 lines checked
next parent reply other threads:[~2021-06-24 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210624151449.39799-1-mohsin.kazmi14@gmail.com>
2021-06-24 15:17 ` checkpatch [this message]
2021-06-24 17:01 ` [dpdk-test-report] |SUCCESS| pw94800 [dpdk-dev] " 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=20210624151746.7821E122E3A@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=mohsin.kazmi14@gmail.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).