automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gregory Etelson <getelson@nvidia.com>
Subject: |WARNING| pw126663 [RFC PATCH v2] ethdev: add indirect list flow action
Date: Tue,  2 May 2023 17:10:23 +0200 (CEST)	[thread overview]
Message-ID: <20230502151023.C1E2A120698@dpdk.org> (raw)
In-Reply-To: <20230502150941.1155-1-getelson@nvidia.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/126663

_coding style issues_


ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#345: FILE: lib/ethdev/rte_flow.h:6228:
+					 rte_flow_indir_action_conf *conf,
 					                            ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#450: FILE: lib/ethdev/rte_flow.h:6333:
+					 rte_flow_action_list_handle *handle,
 					                             ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#497: FILE: lib/ethdev/rte_flow.h:6380:
+					  rte_flow_action_list_handle *handle,
 					                              ^

total: 3 errors, 0 warnings, 331 lines checked

      parent reply	other threads:[~2023-05-02 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230502150941.1155-1-getelson@nvidia.com>
2023-05-02 14:59 ` |SUCCESS| " qemudev
2023-05-02 15:03 ` qemudev
2023-05-02 15:10 ` checkpatch [this message]

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=20230502151023.C1E2A120698@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).