From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nitin Saxena <nsaxena@marvell.com>
Subject: |WARNING| pw154032 [PATCH v11 2/7] graph: add feature arc registrations
Date: Wed, 4 Jun 2025 17:33:32 +0200 (CEST) [thread overview]
Message-ID: <20250604153332.4ABF812527C@dpdk.org> (raw)
In-Reply-To: <20250604153020.92712-3-nsaxena@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/154032
_coding style issues_
WARNING:TYPO_SPELLING: 'Custome' may be misspelled - perhaps 'Custom'?
#401: FILE: doc/guides/prog_guide/graph_lib.rst:826:
+``Custome Feature`` needs to run after ``Feature-1`` it can be defined as shown
WARNING:TYPO_SPELLING: 'Custome' may be misspelled - perhaps 'Custom'?
#402: FILE: doc/guides/prog_guide/graph_lib.rst:827:
+above. Similarly, if ``Feature-2`` needs to run before ``Custome-Feature`` but
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#1311: FILE: lib/graph/rte_graph_feature_arc.h:13:
+#include <stdio.h>
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#1519: FILE: lib/graph/rte_graph_feature_arc.h:221:
+#define RTE_GRAPH_FEATURE_REGISTER(reg) \
+ RTE_INIT(__rte_graph_feature_register_##reg) \
+ { \
+ __rte_graph_feature_register(®, __func__, __LINE__); \
+ }
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#1526: FILE: lib/graph/rte_graph_feature_arc.h:228:
+#define RTE_GRAPH_FEATURE_ARC_REGISTER(reg) \
+ RTE_INIT(__rte_graph_feature_arc_register_##reg) \
+ { \
+ __rte_graph_feature_arc_register(®, __func__, __LINE__); \
+ }
total: 2 errors, 3 warnings, 1408 lines checked
parent reply other threads:[~2025-06-04 15:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250604153020.92712-3-nsaxena@marvell.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=20250604153332.4ABF812527C@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nsaxena@marvell.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).