From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Subject: [dpdk-test-report] |WARNING| pw29895 [PATCH v2 02/26] net/octeontx/base: add octeontx io operations
Date: Sun, 8 Oct 2017 14:45:32 +0200 (CEST) [thread overview]
Message-ID: <20171008124532.EA8591B1AB@dpdk.org> (raw)
In-Reply-To: <20171008124430.1866-3-santosh.shukla@caviumnetworks.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/29895
_coding style issues_
WARNING:BAD_SIGN_OFF: Non-standard signature: Co-authored-by:
#21:
Co-authored-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
ERROR:SPACING: spaces required around that ':' (ctx:ExV)
#89: FILE: drivers/net/octeontx/base/octeontx_io.h:56:
+ :[x0]"=r"(val0), [x1]"=r"(val1) \
^
ERROR:SPACING: spaces required around that ':' (ctx:ExV)
#90: FILE: drivers/net/octeontx/base/octeontx_io.h:57:
+ :[p1]"r"(addr) \
^
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'addr' - possible side-effects?
#102: FILE: drivers/net/octeontx/base/octeontx_io.h:69:
+#define octeontx_load_pair(val0, val1, addr) \
+do { \
+ val0 = rte_read64(addr); \
+ val1 = rte_read64(((uint8_t *)addr) + 8); \
+} while (0)
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'addr' - possible side-effects?
#108: FILE: drivers/net/octeontx/base/octeontx_io.h:75:
+#define octeontx_store_pair(val0, val1, addr) \
+do { \
+ rte_write64(val0, addr); \
+ rte_write64(val1, (((uint8_t *)addr) + 8)); \
+} while (0)
total: 2 errors, 1 warnings, 2 checks, 156 lines checked
parent reply other threads:[~2017-10-08 12:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20171008124430.1866-3-santosh.shukla@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=20171008124532.EA8591B1AB@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=santosh.shukla@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).