From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: |WARNING| pw136557 [RFC 1/5] eal: add static per-lcore memory allocation facility
Date: Thu, 8 Feb 2024 19:25:10 +0100 (CET) [thread overview]
Message-ID: <20240208182510.BE71A121F0B@dpdk.org> (raw)
In-Reply-To: <20240208181644.455233-2-mattias.ronnblom@ericsson.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/136557
_coding style issues_
WARNING:TYPO_SPELLING: 'varible' may be misspelled - perhaps 'variable'?
#177: FILE: doc/api/doxy-api-index.md:101:
+ [lcore-varible](@ref rte_lcore_var.h),
WARNING:TYPO_SPELLING: 'satisify' may be misspelled - perhaps 'satisfy'?
#260: FILE: lib/eal/common/eal_common_lcore_var.c:74:
+ * should satisify alignment requirements of any kind of
WARNING:TYPO_SPELLING: 'endcode' may be misspelled - perhaps 'encode'?
#442: FILE: lib/eal/include/rte_lcore_var.h:146:
+ * ^[ndcode
WARNING:TYPO_SPELLING: 'endcode' may be misspelled - perhaps 'encode'?
#456: FILE: lib/eal/include/rte_lcore_var.h:160:
+ * ^[ndcode
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#522: FILE: lib/eal/include/rte_lcore_var.h:226:
+#define RTE_LCORE_VAR_HANDLE_TYPE(type) \
+ type *
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#538: FILE: lib/eal/include/rte_lcore_var.h:242:
+#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
#544: FILE: lib/eal/include/rte_lcore_var.h:248:
+#define RTE_LCORE_VAR_ALLOC_SZ(name, size) \
+ name = rte_lcore_var_alloc(size)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#558: FILE: lib/eal/include/rte_lcore_var.h:262:
+#define RTE_LCORE_VAR_INIT_SZ(name) \
+ RTE_INIT(rte_lcore_var_init_ ## name) \
+ { \
+ RTE_LCORE_VAR_ALLOC_SZ(name); \
+ }
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#567: FILE: lib/eal/include/rte_lcore_var.h:271:
+#define RTE_LCORE_VAR_INIT(name) \
+ RTE_INIT(rte_lcore_var_init_ ## name) \
+ { \
+ RTE_LCORE_VAR_ALLOC(name); \
+ }
WARNING:TYPO_SPELLING: 'identifer' may be misspelled - perhaps 'identifier'?
#630: FILE: lib/eal/include/rte_lcore_var.h:334:
+ * The pointer returned is only an opaque identifer of the variable. To
total: 5 errors, 5 warnings, 470 lines checked
parent reply other threads:[~2024-02-08 18:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240208181644.455233-2-mattias.ronnblom@ericsson.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=20240208182510.BE71A121F0B@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).