automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stanislaw Kardach <kda@semihalf.com>
Subject: |WARNING| pw110743 [PATCH 03/11] eal: add initial support for RISC-V architecture
Date: Thu,  5 May 2022 19:31:42 +0200 (CEST)	[thread overview]
Message-ID: <20220505173142.16CD81242E3@dpdk.org> (raw)
In-Reply-To: <20220505173003.3242618-4-kda@semihalf.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/110743

_coding style issues_


WARNING:BAD_SIGN_OFF: Non-standard signature: Sponsored-by:
#130: 
Sponsored-by: Frank Zhao <Frank.Zhao@starfivetech.com>

WARNING:BAD_SIGN_OFF: Non-standard signature: Sponsored-by:
#131: 
Sponsored-by: Sam Grove <sam.grove@sifive.com>

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#818: FILE: lib/eal/riscv/include/rte_atomic.h:24:
+#define rte_mb()	asm volatile("fence rw, rw" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#820: FILE: lib/eal/riscv/include/rte_atomic.h:26:
+#define rte_wmb()	asm volatile("fence w, w" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#822: FILE: lib/eal/riscv/include/rte_atomic.h:28:
+#define rte_rmb()	asm volatile("fence r, r" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#830: FILE: lib/eal/riscv/include/rte_atomic.h:36:
+#define rte_io_mb()	asm volatile("fence iorw, iorw" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#832: FILE: lib/eal/riscv/include/rte_atomic.h:38:
+#define rte_io_wmb()	asm volatile("fence orw, ow" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#834: FILE: lib/eal/riscv/include/rte_atomic.h:40:
+#define rte_io_rmb()	asm volatile("fence ir, ir" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#984: FILE: lib/eal/riscv/include/rte_cycles.h:21:
+#define RV64_CSRR(reg, value) \
+	asm volatile("csrr %0, " #reg : "=r" (value) : : "memory")

WARNING:TYPO_SPELLING: 'hart' may be misspelled - perhaps 'heart'?
#1006: FILE: lib/eal/riscv/include/rte_cycles.h:43:
+/** Read hart cycle counter */

WARNING:TYPO_SPELLING: 'hart' may be misspelled - perhaps 'heart'?
#1015: FILE: lib/eal/riscv/include/rte_cycles.h:52:
+/** Read hart cycle counter ensuring no re-ordering */

total: 7 errors, 4 warnings, 1444 lines checked
Warning in lib/eal/riscv/include/rte_vect.h:
Using compiler attribute directly
Warning in lib/eal/riscv/include/rte_atomic.h:
Using rte_smp_[r/w]mb
Warning in lib/eal/riscv/include/rte_atomic.h:
Using __atomic_thread_fence

           reply	other threads:[~2022-05-05 17:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20220505173003.3242618-4-kda@semihalf.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=20220505173142.16CD81242E3@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=kda@semihalf.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).