From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jiawen Wu <jiawenwu@trustnetic.com>
Subject: [dpdk-test-report] |WARNING| pw94335 [PATCH v6 10/19] net/ngbe: support link update
Date: Thu, 17 Jun 2021 13:01:04 +0200 (CEST) [thread overview]
Message-ID: <20210617110104.7D343122E3A@dpdk.org> (raw)
In-Reply-To: <20210617110005.4132926-11-jiawenwu@trustnetic.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/94335
_coding style issues_
WARNING:REPEATED_WORD: Possible repeated word: 'param'
#532: FILE: drivers/net/ngbe/ngbe_ethdev.c:506:
+ * @param param
WARNING:REPEATED_WORD: Possible repeated word: 'param'
#580: FILE: drivers/net/ngbe/ngbe_ethdev.c:554:
+ * @param param
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#613: FILE: drivers/net/ngbe/ngbe_ethdev.h:10:
+#define NGBE_FLAG_NEED_LINK_UPDATE (uint32_t)(1 << 0)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#614: FILE: drivers/net/ngbe/ngbe_ethdev.h:11:
+#define NGBE_FLAG_MAILBOX (uint32_t)(1 << 1)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#615: FILE: drivers/net/ngbe/ngbe_ethdev.h:12:
+#define NGBE_FLAG_PHY_INTERRUPT (uint32_t)(1 << 2)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#616: FILE: drivers/net/ngbe/ngbe_ethdev.h:13:
+#define NGBE_FLAG_MACSEC (uint32_t)(1 << 3)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#617: FILE: drivers/net/ngbe/ngbe_ethdev.h:14:
+#define NGBE_FLAG_NEED_LINK_CONFIG (uint32_t)(1 << 4)
total: 5 errors, 2 warnings, 0 checks, 551 lines checked
parent reply other threads:[~2021-06-17 11:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210617110005.4132926-11-jiawenwu@trustnetic.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=20210617110104.7D343122E3A@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jiawenwu@trustnetic.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).