From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw94440 [PATCH v3 30/62] net/cnxk: add Tx vector version for cn10k
Date: Fri, 18 Jun 2021 12:43:31 +0200 (CEST) [thread overview]
Message-ID: <20210618104331.EE207122E3A@dpdk.org> (raw)
In-Reply-To: <20210618103741.26526-31-ndabilpuram@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/94440
_coding style issues_
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#133: FILE: drivers/net/cnxk/cn10k_tx.h:43:
+#define LMT_OFF(lmt_addr, lmt_num, offset) \
+ (void *)((lmt_addr) + ((lmt_num) << ROC_LMT_LINE_SIZE_LOG2) + (offset))
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#779: FILE: drivers/net/cnxk/cn10k_tx.h:1219:
+ senddesc01_w1 = vaddq_u8(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#781: FILE: drivers/net/cnxk/cn10k_tx.h:1221:
+ senddesc23_w1 = vaddq_u8(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#830: FILE: drivers/net/cnxk/cn10k_tx.h:1270:
+ __mempool_check_cookies(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#837: FILE: drivers/net/cnxk/cn10k_tx.h:1277:
+ __mempool_check_cookies(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#844: FILE: drivers/net/cnxk/cn10k_tx.h:1284:
+ __mempool_check_cookies(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#851: FILE: drivers/net/cnxk/cn10k_tx.h:1291:
+ __mempool_check_cookies(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#866: FILE: drivers/net/cnxk/cn10k_tx.h:1306:
+ __mempool_check_cookies(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#870: FILE: drivers/net/cnxk/cn10k_tx.h:1310:
+ __mempool_check_cookies(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#874: FILE: drivers/net/cnxk/cn10k_tx.h:1314:
+ __mempool_check_cookies(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#878: FILE: drivers/net/cnxk/cn10k_tx.h:1318:
+ __mempool_check_cookies(
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'flags' - possible side-effects?
#990: FILE: drivers/net/cnxk/cn10k_tx_vec.c:8:
+#define T(name, f4, f3, f2, f1, f0, sz, flags) \
+ uint16_t __rte_noinline __rte_hot \
+ cn10k_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 cn10k_nix_xmit_pkts_vector(tx_queue, tx_pkts, pkts, cmd,\
+ (flags)); \
+ }
total: 1 errors, 0 warnings, 11 checks, 905 lines checked
parent reply other threads:[~2021-06-18 10:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210618103741.26526-31-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=20210618104331.EE207122E3A@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).