From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Subject: [dpdk-test-report] |WARNING| pw61494 [RFC v6 6/6] lib/ring: improved copy function to copy ring elements
Date: Mon, 21 Oct 2019 02:24:52 +0200 (CEST) [thread overview]
Message-ID: <20191021002452.1A3422986@dpdk.org> (raw)
In-Reply-To: <20191021002300.26497-7-honnappa.nagarahalli@arm.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/61494
_coding style issues_
ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#126: FILE: lib/librte_ring/rte_ring_elem.h:121:
+ case 7: du32[nr_num - 7] = su32[nr_num - 7]; /* fallthrough */
ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#127: FILE: lib/librte_ring/rte_ring_elem.h:122:
+ case 6: du32[nr_num - 6] = su32[nr_num - 6]; /* fallthrough */
ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#128: FILE: lib/librte_ring/rte_ring_elem.h:123:
+ case 5: du32[nr_num - 5] = su32[nr_num - 5]; /* fallthrough */
ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#129: FILE: lib/librte_ring/rte_ring_elem.h:124:
+ case 4: du32[nr_num - 4] = su32[nr_num - 4]; /* fallthrough */
ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#130: FILE: lib/librte_ring/rte_ring_elem.h:125:
+ case 3: du32[nr_num - 3] = su32[nr_num - 3]; /* fallthrough */
ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#131: FILE: lib/librte_ring/rte_ring_elem.h:126:
+ case 2: du32[nr_num - 2] = su32[nr_num - 2]; /* fallthrough */
ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#132: FILE: lib/librte_ring/rte_ring_elem.h:127:
+ case 1: du32[nr_num - 1] = su32[nr_num - 1]; /* fallthrough */
total: 7 errors, 0 warnings, 183 lines checked
parent reply other threads:[~2019-10-21 0:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20191021002300.26497-7-honnappa.nagarahalli@arm.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=20191021002452.1A3422986@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=honnappa.nagarahalli@arm.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).