automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Feifei Wang <feifei.wang2@arm.com>
Subject: [dpdk-test-report] |WARNING| pw103100 [PATCH v7 1/5] eal: add new definitions for wait scheme
Date: Thu, 28 Oct 2021 08:57:29 +0200 (CEST)	[thread overview]
Message-ID: <20211028065729.DFF901220F5@dpdk.org> (raw)
In-Reply-To: <20211028065640.139655-2-feifei.wang2@arm.com>

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

_coding style issues_


ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#112: FILE: lib/eal/arm/include/rte_pause_64.h:40:
+#define __RTE_ARM_LOAD_EXC_16(src, dst, memorder) {       \
 	if (memorder == __ATOMIC_RELAXED) {               \
 		asm volatile("ldxrh %w[tmp], [%x[addr]]"  \
 			: [tmp] "=&r" (dst)               \

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 17)
#178: FILE: lib/eal/arm/include/rte_pause_64.h:110:
 	if (value != expected) {
+		 __RTE_ARM_SEVL()

total: 1 errors, 1 warnings, 241 lines checked

           reply	other threads:[~2021-10-28  6:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20211028065640.139655-2-feifei.wang2@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=20211028065729.DFF901220F5@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=feifei.wang2@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).