From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: |WARNING| pw145965 [PATCH v12 1/7] eal: add static per-lcore memory allocation facility
Date: Tue, 15 Oct 2024 09:05:46 +0200 (CEST) [thread overview]
Message-ID: <20241015070546.D515F120757@dpdk.org> (raw)
In-Reply-To: <20241015065505.823840-2-mattias.ronnblom@ericsson.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/145965
_coding style issues_
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#842: FILE: lib/eal/include/rte_lcore_var.h:222:
+#define RTE_LCORE_VAR_HANDLE_TYPE(type) \
+ type *
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#857: FILE: lib/eal/include/rte_lcore_var.h:237:
+#define RTE_LCORE_VAR_HANDLE(type, name) \
+ RTE_LCORE_VAR_HANDLE_TYPE(type) name
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#865: FILE: lib/eal/include/rte_lcore_var.h:245:
+#define RTE_LCORE_VAR_ALLOC_SIZE_ALIGN(handle, size, align) \
+ handle = rte_lcore_var_alloc(size, align)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#893: FILE: lib/eal/include/rte_lcore_var.h:273:
+#define RTE_LCORE_VAR_INIT_SIZE_ALIGN(name, size, align) \
+ RTE_INIT(rte_lcore_var_init_ ## name) \
+ { \
+ RTE_LCORE_VAR_ALLOC_SIZE_ALIGN(name, size, align); \
+ }
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#913: FILE: lib/eal/include/rte_lcore_var.h:293:
+#define RTE_LCORE_VAR_INIT(name) \
+ RTE_INIT(rte_lcore_var_init_ ## name) \
+ { \
+ RTE_LCORE_VAR_ALLOC(name); \
+ }
total: 5 errors, 0 warnings, 686 lines checked
Please use __rte_cache_aligned only for struct or union types alignment.
prev parent reply other threads:[~2024-10-15 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241015065505.823840-2-mattias.ronnblom@ericsson.com>
2024-10-15 6:57 ` |WARNING| pw145965-145966 " qemudev
2024-10-15 7:05 ` checkpatch [this message]
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=20241015070546.D515F120757@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=mattias.ronnblom@ericsson.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).