From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Pavan Bhagavatula <pbhagavatula@caviumnetworks.com>
Subject: [dpdk-test-report] |WARNING| pw31869 [PATCH] examples/eventdev_pipeline: add Rx adapter support
Date: Fri, 1 Dec 2017 16:14:58 +0100 (CET) [thread overview]
Message-ID: <20171201151458.7D50D3258@dpdk.org> (raw)
In-Reply-To: <20171201151314.18181-1-pbhagavatula@caviumnetworks.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/31869
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#17:
Use service run iter function for granular control instead of using dedicated
ERROR:CODE_INDENT: code indent should use tabs where possible
#127: FILE: examples/eventdev_pipeline_sw_pmd/main.c:530:
+^I .dequeue_depth = 8,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#128: FILE: examples/eventdev_pipeline_sw_pmd/main.c:531:
+^I .enqueue_depth = 8,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#129: FILE: examples/eventdev_pipeline_sw_pmd/main.c:532:
+^I .new_event_threshold = 1200,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#139: FILE: examples/eventdev_pipeline_sw_pmd/main.c:542:
+ if (ret)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#139: FILE: examples/eventdev_pipeline_sw_pmd/main.c:542:
+ if (ret)$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 13)
#139: FILE: examples/eventdev_pipeline_sw_pmd/main.c:542:
+ if (ret)
+ rte_exit(EXIT_FAILURE, "failed to create rx adapter[%d]",
ERROR:CODE_INDENT: code indent should use tabs where possible
#140: FILE: examples/eventdev_pipeline_sw_pmd/main.c:543:
+ rte_exit(EXIT_FAILURE, "failed to create rx adapter[%d]",$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#140: FILE: examples/eventdev_pipeline_sw_pmd/main.c:543:
+ rte_exit(EXIT_FAILURE, "failed to create rx adapter[%d]",$
total: 5 errors, 4 warnings, 212 lines checked
parent reply other threads:[~2017-12-01 15:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20171201151314.18181-1-pbhagavatula@caviumnetworks.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=20171201151458.7D50D3258@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pbhagavatula@caviumnetworks.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).