From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shyam Shrivastav <shrivastav.shyam@gmail.com>
Subject: [dpdk-test-report] |WARNING| pw21984 [PATCH] Fixed : ip_pipeline firewall port range filtering
Date: Mon, 20 Mar 2017 10:31:40 +0100 (CET) [thread overview]
Message-ID: <20170320093140.55ACD133F@dpdk.org> (raw)
In-Reply-To: <CAGSp03=yrB0UmNzGyNQSSsfXBH=it-u7uKfx9su7EcAVh4hgoA@mail.gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/21984
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#50:
>> pipeline> p 1 firewall add priority 1 ipv4 0.0.0.0 0 0.0.0.0 0 0 65535 80
ERROR:CODE_INDENT: code indent should use tabs where possible
#97: FILE: examples/ip_pipeline/pipeline/pipeline_firewall_be.c:164:
+ .input_index = 3,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#97: FILE: examples/ip_pipeline/pipeline/pipeline_firewall_be.c:164:
+ .input_index = 3,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#106: FILE: examples/ip_pipeline/pipeline/pipeline_firewall_be.c:224:
+ .input_index = 3,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#106: FILE: examples/ip_pipeline/pipeline/pipeline_firewall_be.c:224:
+ .input_index = 3,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#115: FILE: examples/ip_pipeline/pipeline/pipeline_firewall_be.c:285:
+ .input_index = 3,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#115: FILE: examples/ip_pipeline/pipeline/pipeline_firewall_be.c:285:
+ .input_index = 3,$
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 4 errors, 4 warnings, 24 lines checked
parent reply other threads:[~2017-03-20 9:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAGSp03=yrB0UmNzGyNQSSsfXBH=it-u7uKfx9su7EcAVh4hgoA@mail.gmail.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=20170320093140.55ACD133F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=shrivastav.shyam@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).