From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <skori@marvell.com>
Subject: |WARNING| pw131265 [PATCH v3 1/1] app/graph: add example for different usecases
Date: Fri, 8 Sep 2023 12:50:33 +0200 (CEST) [thread overview]
Message-ID: <20230908105033.1B1CE1210A9@dpdk.org> (raw)
In-Reply-To: <20230908104907.4060511-1-skori@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/131265
_coding style issues_
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#188: FILE: app/graph/cli.c:6:
+#include <stdio.h>
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#433: FILE: app/graph/cli.h:37:
+#define CLI_REGISTER(module) \
+ RTE_INIT(cli_register_##module) \
+ { \
+ cli_module_register(&module); \
+ }
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#483: FILE: app/graph/conn.c:8:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#822: FILE: app/graph/ethdev.c:5:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#1851: FILE: app/graph/graph.c:5:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#2295: FILE: app/graph/ip4_route.c:5:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#2447: FILE: app/graph/ip6_route.c:5:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#2610: FILE: app/graph/l3fwd.c:8:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#2785: FILE: app/graph/main.c:8:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#2989: FILE: app/graph/mempool.c:5:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#3246: FILE: app/graph/neigh.c:6:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#3602: FILE: app/graph/utils.c:6:
+#include <stdio.h>
WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#3977: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:11:
+dot -Tsvg dot.dot -o doc/guides/tools/img/graph-usecase-l3fwd.svg
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4027: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:61:
+<text text-anchor="middle" x="436.5" y="-480.3" font-family="Times,serif" font-size="14.00">ingress_port</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4033: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:67:
+<text text-anchor="middle" x="436.5" y="-393.3" font-family="Times,serif" font-size="14.00">ethdev_rx</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4040: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:74:
+<text text-anchor="middle" x="489" y="-436.8" font-family="Times,serif" font-size="14.00">ingress packet</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4046: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:80:
+<text text-anchor="middle" x="436.5" y="-320.3" font-family="Times,serif" font-size="14.00">pkt_cls</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4058: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:92:
+<text text-anchor="middle" x="436.5" y="-247.3" font-family="Times,serif" font-size="14.00">ip4_lookup</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4070: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:104:
+<text text-anchor="middle" x="297.5" y="-247.3" font-family="Times,serif" font-size="14.00">ip6_lookup</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4082: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:116:
+<text text-anchor="middle" x="361.5" y="-14.3" font-family="Times,serif" font-size="14.00">pkt_drop</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4094: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:128:
+<text text-anchor="middle" x="394.5" y="-174.3" font-family="Times,serif" font-size="14.00">ip4_rewrite</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4112: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:146:
+<text text-anchor="middle" x="210.5" y="-174.3" font-family="Times,serif" font-size="14.00">ip6_rewrite</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4130: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:164:
+<text text-anchor="middle" x="249.5" y="-101.3" font-family="Times,serif" font-size="14.00">ethdev_tx</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4166: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:200:
+<text text-anchor="middle" x="50.5" y="-14.3" font-family="Times,serif" font-size="14.00">egress_port</text>
WARNING:REPEATED_WORD: Possible repeated word: 'text'
#4173: FILE: doc/guides/tools/img/graph-usecase-l3fwd.svg:207:
+<text text-anchor="middle" x="211.5" y="-57.8" font-family="Times,serif" font-size="14.00">egress packet</text>
total: 1 errors, 24 warnings, 3815 lines checked
next parent reply other threads:[~2023-09-08 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230908104907.4060511-1-skori@marvell.com>
2023-09-08 10:50 ` checkpatch [this message]
2023-09-08 11:39 ` |FAILURE| " 0-day Robot
2023-09-12 13:11 ` |SUCCESS| " qemudev
2023-09-12 13:15 ` qemudev
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=20230908105033.1B1CE1210A9@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=skori@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).