From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
Subject: [dpdk-test-report] |WARNING| pw22782 [PATCH v5 16/62] net/qede/base: read card personality via MFW commands
Date: Thu, 30 Mar 2017 02:10:25 +0200 (CEST) [thread overview]
Message-ID: <20170330001025.F3C03FBBB@dpdk.org> (raw)
In-Reply-To: <1490819822-27267-17-git-send-email-rasesh.mody@cavium.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/22782
_coding style issues_
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'dev' - possible side-effects?
#44: FILE: drivers/net/qede/base/ecore.h:332:
+#define ECORE_IS_RDMA_PERSONALITY(dev) \
+ ((dev)->hw_info.personality == ECORE_PCI_ETH_ROCE || \
+ (dev)->hw_info.personality == ECORE_PCI_ETH_IWARP || \
+ (dev)->hw_info.personality == ECORE_PCI_ETH_RDMA)
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'dev' - possible side-effects?
#48: FILE: drivers/net/qede/base/ecore.h:336:
+#define ECORE_IS_ROCE_PERSONALITY(dev) \
+ ((dev)->hw_info.personality == ECORE_PCI_ETH_ROCE || \
+ (dev)->hw_info.personality == ECORE_PCI_ETH_RDMA)
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'dev' - possible side-effects?
#51: FILE: drivers/net/qede/base/ecore.h:339:
+#define ECORE_IS_IWARP_PERSONALITY(dev) \
+ ((dev)->hw_info.personality == ECORE_PCI_ETH_IWARP || \
+ (dev)->hw_info.personality == ECORE_PCI_ETH_RDMA)
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'dev' - possible side-effects?
#54: FILE: drivers/net/qede/base/ecore.h:342:
+#define ECORE_IS_L2_PERSONALITY(dev) \
+ ((dev)->hw_info.personality == ECORE_PCI_ETH || \
+ ECORE_IS_RDMA_PERSONALITY(dev))
total: 0 errors, 0 warnings, 4 checks, 156 lines checked
parent reply other threads:[~2017-03-30 0:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1490819822-27267-17-git-send-email-rasesh.mody@cavium.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=20170330001025.F3C03FBBB@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=Rasesh.Mody@cavium.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).