From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw82835 [PATCH] pipeline: increase immediate operand size
Date: Thu, 29 Oct 2020 19:08:42 +0100 (CET) [thread overview]
Message-ID: <20201029180842.AA9FCC8F4@dpdk.org> (raw)
In-Reply-To: <20201029180810.49636-1-cristian.dumitrescu@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/82835
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#474: FILE: lib/librte_pipeline/rte_swx_pipeline.h:374:
+ *<pre>| I | Immediate value (64-bit) | h.header.field | NO | YES |</pre>$
WARNING:SPACING: space prohibited between function name and open parenthesis '('
#474: FILE: lib/librte_pipeline/rte_swx_pipeline.h:374:
+ *<pre>| I | Immediate value (64-bit) | h.header.field | NO | YES |</pre>
ERROR:SPACING: spaces required around that '<' (ctx:OxV)
#474: FILE: lib/librte_pipeline/rte_swx_pipeline.h:374:
+ *<pre>| I | Immediate value (64-bit) | h.header.field | NO | YES |</pre>
^
ERROR:SPACING: spaces required around that '>' (ctx:VxO)
#474: FILE: lib/librte_pipeline/rte_swx_pipeline.h:374:
+ *<pre>| I | Immediate value (64-bit) | h.header.field | NO | YES |</pre>
^
ERROR:SPACING: need consistent spacing around '|' (ctx:OxW)
#474: FILE: lib/librte_pipeline/rte_swx_pipeline.h:374:
+ *<pre>| I | Immediate value (64-bit) | h.header.field | NO | YES |</pre>
^
ERROR:SPACING: need consistent spacing around '|' (ctx:WxO)
#474: FILE: lib/librte_pipeline/rte_swx_pipeline.h:374:
+ *<pre>| I | Immediate value (64-bit) | h.header.field | NO | YES |</pre>
^
ERROR:SPACING: spaces required around that '<' (ctx:OxO)
#474: FILE: lib/librte_pipeline/rte_swx_pipeline.h:374:
+ *<pre>| I | Immediate value (64-bit) | h.header.field | NO | YES |</pre>
^
ERROR:SPACING: spaces required around that '>' (ctx:VxE)
#474: FILE: lib/librte_pipeline/rte_swx_pipeline.h:374:
+ *<pre>| I | Immediate value (64-bit) | h.header.field | NO | YES |</pre>
^
total: 6 errors, 2 warnings, 365 lines checked
next parent reply other threads:[~2020-10-29 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201029180810.49636-1-cristian.dumitrescu@intel.com>
2020-10-29 18:08 ` checkpatch [this message]
2020-10-29 22:27 ` [dpdk-test-report] |SUCCESS| pw82835 " 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=20201029180842.AA9FCC8F4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=cristian.dumitrescu@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).