From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw64806 [PATCH V4 10/10] net/bnxt: fix to cap max rings to minimum of compl rings and stat contexts
Date: Thu, 16 Jan 2020 13:50:29 +0100 (CET) [thread overview]
Message-ID: <20200116125029.58DAA1D52F@dpdk.org> (raw)
In-Reply-To: <20200116130455.30193-11-kalesh-anakkur.purayil@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/64806
_coding style issues_
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'bp' - possible side-effects?
#85: FILE: drivers/net/bnxt/bnxt.h:626:
+#define BNXT_MAX_RX_RINGS(bp) \
(BNXT_STINGRAY(bp) ? RTE_MIN(RTE_MIN(bp->max_rx_rings, \
MAX_STINGRAY_RINGS), \
+ bp->max_stat_ctx / 2U) : \
+ RTE_MIN(bp->max_rx_rings, \
+ bp->max_stat_ctx / 2U))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'bp' - possible side-effects?
#93: FILE: drivers/net/bnxt/bnxt.h:632:
+#define BNXT_MAX_TX_RINGS(bp) \
+ (RTE_MIN((bp)->max_tx_rings, BNXT_MAX_RX_RINGS(bp)))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'bp' - possible side-effects?
#96: FILE: drivers/net/bnxt/bnxt.h:635:
+#define BNXT_MAX_RINGS(bp) \
+ (RTE_MIN((((bp)->max_cp_rings - BNXT_NUM_ASYNC_CPR(bp)) / 2U), \
+ BNXT_MAX_TX_RINGS(bp)))
total: 0 errors, 0 warnings, 3 checks, 22 lines checked
next parent reply other threads:[~2020-01-16 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200116130455.30193-11-kalesh-anakkur.purayil@broadcom.com>
2020-01-16 12:50 ` checkpatch [this message]
2020-01-16 20:00 ` [dpdk-test-report] |SUCCESS| pw64806 net/bnxt: fix to use correct IOVA mapping 0-day Robot
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=20200116125029.58DAA1D52F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=kalesh-anakkur.purayil@broadcom.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).