automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw94433 [PATCH v3 24/62] net/cnxk: add Tx vector version for cn9k
Date: Fri, 18 Jun 2021 12:42:55 +0200 (CEST)	[thread overview]
Message-ID: <20210618104255.B1467122E3A@dpdk.org> (raw)
In-Reply-To: <20210618103741.26526-25-ndabilpuram@marvell.com>

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

_coding style issues_


CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#723: FILE: drivers/net/cnxk/cn9k_tx.h:1082:
+			senddesc01_w1 = vaddq_u8(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#725: FILE: drivers/net/cnxk/cn9k_tx.h:1084:
+			senddesc23_w1 = vaddq_u8(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#774: FILE: drivers/net/cnxk/cn9k_tx.h:1133:
+				__mempool_check_cookies(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#781: FILE: drivers/net/cnxk/cn9k_tx.h:1140:
+				__mempool_check_cookies(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#788: FILE: drivers/net/cnxk/cn9k_tx.h:1147:
+				__mempool_check_cookies(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#795: FILE: drivers/net/cnxk/cn9k_tx.h:1154:
+				__mempool_check_cookies(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#814: FILE: drivers/net/cnxk/cn9k_tx.h:1173:
+			__mempool_check_cookies(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#818: FILE: drivers/net/cnxk/cn9k_tx.h:1177:
+			__mempool_check_cookies(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#822: FILE: drivers/net/cnxk/cn9k_tx.h:1181:
+			__mempool_check_cookies(

CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#826: FILE: drivers/net/cnxk/cn9k_tx.h:1185:
+			__mempool_check_cookies(

CHECK:MACRO_ARG_REUSE: Macro argument reuse 'flags' - possible side-effects?
#905: FILE: drivers/net/cnxk/cn9k_tx_vec.c:8:
+#define T(name, f4, f3, f2, f1, f0, sz, flags)				       \
+	uint16_t __rte_noinline __rte_hot				       \
+		cn9k_nix_xmit_pkts_vec_##name(void *tx_queue,                  \
+					      struct rte_mbuf **tx_pkts,       \
+					      uint16_t pkts)                   \
+	{                                                                      \
+		uint64_t cmd[sz];                                              \
+									       \
+		/* VLAN, TSTMP, TSO is not supported by vec */                 \
+		if ((flags) & NIX_TX_OFFLOAD_VLAN_QINQ_F ||		       \
+		    (flags) & NIX_TX_OFFLOAD_TSO_F)			       \
+			return 0;                                              \
+		return cn9k_nix_xmit_pkts_vector(tx_queue, tx_pkts, pkts, cmd, \
+						 (flags));		       \
+	}

total: 0 errors, 0 warnings, 11 checks, 823 lines checked

           reply	other threads:[~2021-06-18 10:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210618103741.26526-25-ndabilpuram@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=20210618104255.B1467122E3A@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=ndabilpuram@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).