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: |WARNING| pw144471 [PATCH v2 13/18] net/cnxk: support Rx burst scalar for cn20k
Date: Thu, 26 Sep 2024 18:09:12 +0200 (CEST)	[thread overview]
Message-ID: <20240926160912.8E4EC121D9E@dpdk.org> (raw)
In-Reply-To: <20240926160158.3206321-14-ndabilpuram@marvell.com>

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

_coding style issues_


CHECK:MACRO_ARG_REUSE: Macro argument reuse 'b' - possible side-effects?
#291: FILE: drivers/net/cnxk/cn20k_rx.h:37:
+#define CQE_PTR_OFF(b, i, o, f)                                                                    \
+	(((f) & NIX_RX_VWQE_F) ? (uint64_t *)(((uintptr_t)((uint64_t *)(b))[i]) + (o)) :           \
+				 (uint64_t *)(((uintptr_t)(b)) + CQE_SZ(i) + (o)))

CHECK:MACRO_ARG_REUSE: Macro argument reuse 'i' - possible side-effects?
#291: FILE: drivers/net/cnxk/cn20k_rx.h:37:
+#define CQE_PTR_OFF(b, i, o, f)                                                                    \
+	(((f) & NIX_RX_VWQE_F) ? (uint64_t *)(((uintptr_t)((uint64_t *)(b))[i]) + (o)) :           \
+				 (uint64_t *)(((uintptr_t)(b)) + CQE_SZ(i) + (o)))

CHECK:MACRO_ARG_REUSE: Macro argument reuse 'o' - possible side-effects?
#291: FILE: drivers/net/cnxk/cn20k_rx.h:37:
+#define CQE_PTR_OFF(b, i, o, f)                                                                    \
+	(((f) & NIX_RX_VWQE_F) ? (uint64_t *)(((uintptr_t)((uint64_t *)(b))[i]) + (o)) :           \
+				 (uint64_t *)(((uintptr_t)(b)) + CQE_SZ(i) + (o)))

CHECK:MACRO_ARG_REUSE: Macro argument reuse 'b' - possible side-effects?
#294: FILE: drivers/net/cnxk/cn20k_rx.h:40:
+#define CQE_PTR_DIFF(b, i, o, f)                                                                   \
+	(((f) & NIX_RX_VWQE_F) ? (uint64_t *)(((uintptr_t)((uint64_t *)(b))[i]) - (o)) :           \
+				 (uint64_t *)(((uintptr_t)(b)) + CQE_SZ(i) - (o)))

CHECK:MACRO_ARG_REUSE: Macro argument reuse 'i' - possible side-effects?
#294: FILE: drivers/net/cnxk/cn20k_rx.h:40:
+#define CQE_PTR_DIFF(b, i, o, f)                                                                   \
+	(((f) & NIX_RX_VWQE_F) ? (uint64_t *)(((uintptr_t)((uint64_t *)(b))[i]) - (o)) :           \
+				 (uint64_t *)(((uintptr_t)(b)) + CQE_SZ(i) - (o)))

CHECK:MACRO_ARG_REUSE: Macro argument reuse 'o' - possible side-effects?
#294: FILE: drivers/net/cnxk/cn20k_rx.h:40:
+#define CQE_PTR_DIFF(b, i, o, f)                                                                   \
+	(((f) & NIX_RX_VWQE_F) ? (uint64_t *)(((uintptr_t)((uint64_t *)(b))[i]) - (o)) :           \
+				 (uint64_t *)(((uintptr_t)(b)) + CQE_SZ(i) - (o)))

WARNING:BRACES: braces {} are not necessary for single statement blocks
#309: FILE: drivers/net/cnxk/cn20k_rx.h:55:
+	if (m->nb_segs == 1 && m->next) {
+		rte_panic("mbuf->next[%p] valid when mbuf->nb_segs is %d", m->next, m->nb_segs);
+	}

total: 0 errors, 1 warnings, 6 checks, 756 lines checked
Warning in drivers/net/cnxk/cn20k_rx.h:
Using rte_panic/rte_exit

           reply	other threads:[~2024-09-26 16:09 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240926160158.3206321-14-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=20240926160912.8E4EC121D9E@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).