automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: [dpdk-test-report] |WARNING| pw66405 [PATCH] eal/arm64: remove internal macros
Date: Mon,  9 Mar 2020 10:39:53 +0100 (CET)	[thread overview]
Message-ID: <20200309093953.C2CC11C038@dpdk.org> (raw)
In-Reply-To: <20200309093844.30579-1-david.marchand@redhat.com>

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

_coding style issues_


ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#86: FILE: lib/librte_eal/common/include/arch/arm/rte_atomic_64.h:22:
+#define rte_mb() asm volatile("dsb sy" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#89: FILE: lib/librte_eal/common/include/arch/arm/rte_atomic_64.h:24:
+#define rte_wmb() asm volatile("dsb st" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#92: FILE: lib/librte_eal/common/include/arch/arm/rte_atomic_64.h:26:
+#define rte_rmb() asm volatile("dsb ld" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#95: FILE: lib/librte_eal/common/include/arch/arm/rte_atomic_64.h:28:
+#define rte_smp_mb() asm volatile("dmb ish" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#98: FILE: lib/librte_eal/common/include/arch/arm/rte_atomic_64.h:30:
+#define rte_smp_wmb() asm volatile("dmb ishst" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#103: FILE: lib/librte_eal/common/include/arch/arm/rte_atomic_64.h:32:
+#define rte_smp_rmb() asm volatile("dmb ishld" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#112: FILE: lib/librte_eal/common/include/arch/arm/rte_atomic_64.h:40:
+#define rte_cio_wmb() asm volatile("dmb oshst" : : : "memory")

ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#115: FILE: lib/librte_eal/common/include/arch/arm/rte_atomic_64.h:42:
+#define rte_cio_rmb() asm volatile("dmb oshld" : : : "memory")

total: 8 errors, 0 warnings, 37 lines checked

       reply	other threads:[~2020-03-09  9:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200309093844.30579-1-david.marchand@redhat.com>
2020-03-09  9:39 ` checkpatch [this message]
2020-03-09 12:04 ` [dpdk-test-report] |SUCCESS| pw66405 " 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=20200309093953.C2CC11C038@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=david.marchand@redhat.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).