From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stanislaw Kardach <kda@semihalf.com>
Subject: |WARNING| pw112452 [PATCH RESEND v4 1/8] eal: add initial support for RISC-V architecture
Date: Tue, 7 Jun 2022 12:47:41 +0200 (CEST) [thread overview]
Message-ID: <20220607104741.95F3C120945@dpdk.org> (raw)
In-Reply-To: <20220607104617.153892-2-kda@semihalf.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/112452
_coding style issues_
WARNING:BAD_SIGN_OFF: Non-standard signature: Sponsored-by:
#137:
Sponsored-by: Frank Zhao <Frank.Zhao@starfivetech.com>
WARNING:BAD_SIGN_OFF: Non-standard signature: Sponsored-by:
#138:
Sponsored-by: Sam Grove <sam.grove@sifive.com>
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#815: 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
#817: 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
#819: 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
#827: 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
#829: 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
#831: FILE: lib/eal/riscv/include/rte_atomic.h:40:
+#define rte_io_rmb() asm volatile("fence ir, ir" : : : "memory")
WARNING:TYPO_SPELLING: 'hart' may be misspelled - perhaps 'heart'?
#998: FILE: lib/eal/riscv/include/rte_cycles.h:38:
+/** Read hart cycle counter */
WARNING:TYPO_SPELLING: 'hart' may be misspelled - perhaps 'heart'?
#1007: FILE: lib/eal/riscv/include/rte_cycles.h:47:
+/** Read hart cycle counter ensuring no re-ordering */
total: 6 errors, 4 warnings, 1424 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
parent reply other threads:[~2022-06-07 10:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220607104617.153892-2-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=20220607104741.95F3C120945@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).