automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chengwen Feng <fengchengwen@huawei.com>
Subject: |WARNING| pw135880 [PATCH v2] bus/uacce: introduce UACCE bus
Date: Tue, 16 Jan 2024 04:41:08 +0100 (CET)	[thread overview]
Message-ID: <20240116034108.9D607122B9B@dpdk.org> (raw)
In-Reply-To: <20240116033543.24844-1-fengchengwen@huawei.com>

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

_coding style issues_


ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#384: FILE: drivers/bus/uacce/bus_uacce_driver.h:242:
+#define RTE_PMD_REGISTER_UACCE(nm, uacce_drv) \
+		RTE_INIT(uacceinitfn_ ##nm) \
+		{\
+			(uacce_drv).driver.name = RTE_STR(nm);\
+			rte_uacce_register(&uacce_drv); \
+		} \
+		RTE_PMD_EXPORT_NAME(nm, __COUNTER__)

total: 1 errors, 0 warnings, 1011 lines checked

  parent reply	other threads:[~2024-01-16  3:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240116033543.24844-1-fengchengwen@huawei.com>
2024-01-16  3:17 ` |SUCCESS| " qemudev
2024-01-16  3:21 ` qemudev
2024-01-16  3:41 ` checkpatch [this message]
2024-01-16  4:29 ` 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=20240116034108.9D607122B9B@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=fengchengwen@huawei.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).