From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Suanming Mou <suanmingm@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw95734 [PATCH v6 03/26] net/mlx5: add index pool foreach define
Date: Tue, 13 Jul 2021 10:46:01 +0200 (CEST) [thread overview]
Message-ID: <20210713084601.6F8AF120F1F@dpdk.org> (raw)
In-Reply-To: <20210713084500.19964-4-suanmingm@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/95734
_coding style issues_
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'ipool' - possible side-effects?
#261: FILE: drivers/net/mlx5/mlx5_utils.h:868:
+#define MLX5_IPOOL_FOREACH(ipool, idx, entry) \
+ for ((idx) = 0, mlx5_ipool_flush_cache((ipool)), \
+ (entry) = mlx5_ipool_get_next((ipool), &idx); \
+ (entry); idx++, (entry) = mlx5_ipool_get_next((ipool), &idx))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'idx' - possible side-effects?
#261: FILE: drivers/net/mlx5/mlx5_utils.h:868:
+#define MLX5_IPOOL_FOREACH(ipool, idx, entry) \
+ for ((idx) = 0, mlx5_ipool_flush_cache((ipool)), \
+ (entry) = mlx5_ipool_get_next((ipool), &idx); \
+ (entry); idx++, (entry) = mlx5_ipool_get_next((ipool), &idx))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'entry' - possible side-effects?
#261: FILE: drivers/net/mlx5/mlx5_utils.h:868:
+#define MLX5_IPOOL_FOREACH(ipool, idx, entry) \
+ for ((idx) = 0, mlx5_ipool_flush_cache((ipool)), \
+ (entry) = mlx5_ipool_get_next((ipool), &idx); \
+ (entry); idx++, (entry) = mlx5_ipool_get_next((ipool), &idx))
total: 0 errors, 0 warnings, 3 checks, 126 lines checked
parent reply other threads:[~2021-07-13 8:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210713084500.19964-4-suanmingm@nvidia.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=20210713084601.6F8AF120F1F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=suanmingm@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).