From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Matan Azrad <matan@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw35064 [PATCH v4 2/2] net/failsafe: fix calling device during RMV events
Date: Thu, 8 Feb 2018 13:22:18 +0100 (CET) [thread overview]
Message-ID: <20180208122218.9B0611B7C9@dpdk.org> (raw)
In-Reply-To: <1518092427-4333-3-git-send-email-matan@mellanox.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/35064
_coding style issues_
CHECK:MACRO_ARG_REUSE: Macro argument reuse 's' - possible side-effects?
#337: FILE: drivers/net/failsafe/failsafe_private.h:266:
+#define FOREACH_SUBDEV_STATE_SAFE(s, i, dev, state) \
+ for (s = fs_find_next((dev), 0, state, 1, &i); \
+ s != NULL; \
+ s = fs_find_next((dev), i + 1, state, 1, &i))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'i' - possible side-effects?
#337: FILE: drivers/net/failsafe/failsafe_private.h:266:
+#define FOREACH_SUBDEV_STATE_SAFE(s, i, dev, state) \
+ for (s = fs_find_next((dev), 0, state, 1, &i); \
+ s != NULL; \
+ s = fs_find_next((dev), i + 1, state, 1, &i))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'dev' - possible side-effects?
#337: FILE: drivers/net/failsafe/failsafe_private.h:266:
+#define FOREACH_SUBDEV_STATE_SAFE(s, i, dev, state) \
+ for (s = fs_find_next((dev), 0, state, 1, &i); \
+ s != NULL; \
+ s = fs_find_next((dev), i + 1, state, 1, &i))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'state' - possible side-effects?
#337: FILE: drivers/net/failsafe/failsafe_private.h:266:
+#define FOREACH_SUBDEV_STATE_SAFE(s, i, dev, state) \
+ for (s = fs_find_next((dev), 0, state, 1, &i); \
+ s != NULL; \
+ s = fs_find_next((dev), i + 1, state, 1, &i))
total: 0 errors, 0 warnings, 4 checks, 269 lines checked
parent reply other threads:[~2018-02-08 12:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1518092427-4333-3-git-send-email-matan@mellanox.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=20180208122218.9B0611B7C9@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=matan@mellanox.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).