From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Lukas Sismis <sismis@dyna-nic.com>
Subject: |WARNING| pw159598 [PATCH v1 3/5] examples/flow_parsing: add flow parser demo
Date: Mon, 5 Jan 2026 22:34:00 +0100 (CET) [thread overview]
Message-ID: <20260105213400.D6169124270@dpdk.org> (raw)
In-Reply-To: <20260105213025.749383-4-sismis@dyna-nic.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159598
_coding style issues_
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#141: FILE: examples/flow_parsing/main.c:27:
+#include <stdio.h>
^^^^^
WARNING:STATIC_CONST_CHAR_ARRAY: static const char * array should probably be static const char * const
#285: FILE: examples/flow_parsing/main.c:171:
+ static const char *attr_strings[] = {
WARNING:BRACES: braces {} are not necessary for any arm of this statement
#303: FILE: examples/flow_parsing/main.c:189:
+ if (ret == 0) {
[...]
+ } else {
[...]
WARNING:STATIC_CONST_CHAR_ARRAY: static const char * array should probably be static const char * const
#318: FILE: examples/flow_parsing/main.c:204:
+ static const char *pattern_strings[] = {
WARNING:BRACES: braces {} are not necessary for any arm of this statement
#337: FILE: examples/flow_parsing/main.c:223:
+ if (ret == 0) {
[...]
+ } else {
[...]
WARNING:STATIC_CONST_CHAR_ARRAY: static const char * array should probably be static const char * const
#352: FILE: examples/flow_parsing/main.c:238:
+ static const char *action_strings[] = {
WARNING:BRACES: braces {} are not necessary for any arm of this statement
#371: FILE: examples/flow_parsing/main.c:257:
+ if (ret == 0) {
[...]
+ } else {
[...]
WARNING:TYPO_SPELLING: 'nIn' may be misspelled - perhaps 'inn'?
#433: FILE: examples/flow_parsing/main.c:319:
+ printf("
In a real application, copy pattern/actions to your own storage,
");
^^^
total: 0 errors, 8 warnings, 366 lines checked
parent reply other threads:[~2026-01-05 21:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260105213025.749383-4-sismis@dyna-nic.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=20260105213400.D6169124270@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=sismis@dyna-nic.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).