From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rashmi Shetty <rashmi.shetty@intel.com>
Subject: [dpdk-test-report] |WARNING| pw101271 [PATCH] app/test-eventdev: add burst enqueue support in perf_queue test
Date: Tue, 12 Oct 2021 23:06:02 +0200 (CEST) [thread overview]
Message-ID: <20211012210602.6066A121D26@dpdk.org> (raw)
In-Reply-To: <20211012210532.78287-1-rashmi.shetty@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/101271
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#53:
for eventdev enqueue at producer in perf_queue test. The newly added function
ERROR:CODE_INDENT: code indent should use tabs where possible
#211: FILE: app/test-eventdev/test_perf_common.c:127:
+ enq = rte_event_enqueue_burst(dev_id, port, ev, burst_size);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#211: FILE: app/test-eventdev/test_perf_common.c:127:
+ enq = rte_event_enqueue_burst(dev_id, port, ev, burst_size);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#212: FILE: app/test-eventdev/test_perf_common.c:128:
+ while (enq < burst_size) {$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#212: FILE: app/test-eventdev/test_perf_common.c:128:
+ while (enq < burst_size) {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#213: FILE: app/test-eventdev/test_perf_common.c:129:
+ enq += rte_event_enqueue_burst(dev_id, port,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#213: FILE: app/test-eventdev/test_perf_common.c:129:
+ enq += rte_event_enqueue_burst(dev_id, port,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#214: FILE: app/test-eventdev/test_perf_common.c:130:
+ ev + enq,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#214: FILE: app/test-eventdev/test_perf_common.c:130:
+ ev + enq,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#216: FILE: app/test-eventdev/test_perf_common.c:132:
+ if (t->done)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#216: FILE: app/test-eventdev/test_perf_common.c:132:
+ if (t->done)$
ERROR:CODE_INDENT: code indent should use tabs where possible
#217: FILE: app/test-eventdev/test_perf_common.c:133:
+ break;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#217: FILE: app/test-eventdev/test_perf_common.c:133:
+ break;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#222: FILE: app/test-eventdev/test_perf_common.c:138:
+ }$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#222: FILE: app/test-eventdev/test_perf_common.c:138:
+ }$
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#240: FILE: app/test-eventdev/test_perf_common.c:282:
+ * perf_producer_burst depending on producer enqueue burst size. */
total: 7 errors, 9 warnings, 172 lines checked
next parent reply other threads:[~2021-10-12 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211012210532.78287-1-rashmi.shetty@intel.com>
2021-10-12 21:06 ` checkpatch [this message]
2021-10-12 21:38 ` [dpdk-test-report] |SUCCESS| pw101271 [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=20211012210602.6066A121D26@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rashmi.shetty@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).