From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gregory Etelson <getelson@nvidia.com>
Subject: |WARNING| pw127380 [PATCH v5 1/2] ethdev: add indirect list flow action
Date: Thu, 25 May 2023 10:13:25 +0200 (CEST) [thread overview]
Message-ID: <20230525081325.D9C77120927@dpdk.org> (raw)
In-Reply-To: <20230525081216.43604-1-getelson@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/127380
_coding style issues_
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#479: FILE: app/test-pmd/cmdline_flow.c:10515:
+ void __rte_unused *buf, unsigned int __rte_unused size)
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#1244: FILE: lib/ethdev/rte_flow.c:2230:
+ rte_flow_indir_action_conf *conf,
^
WARNING:FUNCTION_ARGUMENTS: arguments for function declarations should follow identifier
#1273: FILE: lib/ethdev/rte_flow.c:2259:
+int
WARNING:FUNCTION_ARGUMENTS: arguments for function declarations should follow identifier
#1300: FILE: lib/ethdev/rte_flow.c:2286:
+int
WARNING:FUNCTION_ARGUMENTS: arguments for function declarations should follow identifier
#1327: FILE: lib/ethdev/rte_flow.c:2313:
+int
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#1480: FILE: lib/ethdev/rte_flow.h:6227:
+ rte_flow_indir_action_conf *conf,
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#1592: FILE: lib/ethdev/rte_flow.h:6339:
+ rte_flow_action_list_handle *handle,
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#1637: FILE: lib/ethdev/rte_flow.h:6384:
+ rte_flow_action_list_handle *handle,
^
total: 5 errors, 3 warnings, 1390 lines checked
parent reply other threads:[~2023-05-25 8:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230525081216.43604-1-getelson@nvidia.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=20230525081325.D9C77120927@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=getelson@nvidia.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).