automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Qi Zhang <qi.z.zhang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw76699 [PATCH 13/40] net/ice/base: introduce and use for each bit iterator
Date: Wed,  9 Sep 2020 01:48:06 +0200 (CEST)	[thread overview]
Message-ID: <20200908234806.D81814C99@dpdk.org> (raw)
In-Reply-To: <20200907112826.48493-14-qi.z.zhang@intel.com>

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

_coding style issues_


CHECK:MACRO_ARG_REUSE: Macro argument reuse '_bitpos' - possible side-effects?
#133: FILE: drivers/net/ice/base/ice_bitops.h:349:
+#define ice_for_each_set_bit(_bitpos, _addr, _maxlen)	\
+	for ((_bitpos) = ice_find_first_bit((_addr), (_maxlen)); \
+	     (_bitpos) < (_maxlen); \
+	     (_bitpos) = ice_find_next_bit((_addr), (_maxlen), (_bitpos) + 1))

CHECK:MACRO_ARG_REUSE: Macro argument reuse '_addr' - possible side-effects?
#133: FILE: drivers/net/ice/base/ice_bitops.h:349:
+#define ice_for_each_set_bit(_bitpos, _addr, _maxlen)	\
+	for ((_bitpos) = ice_find_first_bit((_addr), (_maxlen)); \
+	     (_bitpos) < (_maxlen); \
+	     (_bitpos) = ice_find_next_bit((_addr), (_maxlen), (_bitpos) + 1))

CHECK:MACRO_ARG_REUSE: Macro argument reuse '_maxlen' - possible side-effects?
#133: FILE: drivers/net/ice/base/ice_bitops.h:349:
+#define ice_for_each_set_bit(_bitpos, _addr, _maxlen)	\
+	for ((_bitpos) = ice_find_first_bit((_addr), (_maxlen)); \
+	     (_bitpos) < (_maxlen); \
+	     (_bitpos) = ice_find_next_bit((_addr), (_maxlen), (_bitpos) + 1))

total: 0 errors, 0 warnings, 3 checks, 369 lines checked

           reply	other threads:[~2020-09-08 23:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20200907112826.48493-14-qi.z.zhang@intel.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=20200908234806.D81814C99@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=qi.z.zhang@intel.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).