From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Dekel Peled <dekelp@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw52584 [PATCH v3 1/3] ethdev: add actions to modify TCP header fields
Date: Wed, 10 Apr 2019 13:30:00 +0200 (CEST) [thread overview]
Message-ID: <20190410113000.3F2F85942@dpdk.org> (raw)
In-Reply-To: <0235680ea84ba74d3ecebb62bf5af19559c5170e.1554894982.git.dekelp@mellanox.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/52584
_coding style issues_
ERROR:TRAILING_WHITESPACE: trailing whitespace
#49: FILE: doc/guides/prog_guide/rte_flow.rst:2353:
+Using this action on non-matching traffic will result in undefined behavior, $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#67: FILE: doc/guides/prog_guide/rte_flow.rst:2371:
+Using this action on non-matching traffic will result in undefined behavior, $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#85: FILE: doc/guides/prog_guide/rte_flow.rst:2389:
+Using this action on non-matching traffic will result in undefined behavior, $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#103: FILE: doc/guides/prog_guide/rte_flow.rst:2407:
+Using this action on non-matching traffic will result in undefined behavior, $
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#193: FILE: lib/librte_ethdev/rte_flow.h:2170:
+ * General integer type, can be expanded as needed.
+*/
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#195: FILE: lib/librte_ethdev/rte_flow.h:2172:
+ rte_be32_t be32;$
total: 4 errors, 2 warnings, 160 lines checked
parent reply other threads:[~2019-04-10 11:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0235680ea84ba74d3ecebb62bf5af19559c5170e.1554894982.git.dekelp@mellanox.com>]
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=20190410113000.3F2F85942@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=dekelp@mellanox.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).