From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Matan Azrad <matan@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw65266 [PATCH v3 24/25] common/mlx5: share Netlink commands
Date: Tue, 28 Jan 2020 17:34:07 +0100 (CET) [thread overview]
Message-ID: <20200128163407.E01FE1C1D3@dpdk.org> (raw)
In-Reply-To: <1580228860-10665-25-git-send-email-matan@mellanox.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/65266
_coding style issues_
WARNING:RETURN_VOID: void function return statements are not generally useful
#176: FILE: drivers/common/mlx5/mlx5_common.c:163:
+ return;
+}
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#199: FILE: drivers/common/mlx5/mlx5_common.h:31:
+#define BITFIELD_DECLARE(bf, type, size) \
+ type bf[(((size_t)(size) / (sizeof(type) * CHAR_BIT)) + \
+ !!((size_t)(size) % (sizeof(type) * CHAR_BIT)))]
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#202: FILE: drivers/common/mlx5/mlx5_common.h:34:
+#define BITFIELD_DEFINE(bf, type, size) \
+ BITFIELD_DECLARE((bf), type, (size)) = { 0 }
total: 2 errors, 1 warnings, 0 checks, 1687 lines checked
ERROR: symbol mlx5_nl_allmulti is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_ifindex is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_init is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_mac_addr_add is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_mac_addr_flush is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_mac_addr_remove is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_mac_addr_sync is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_portnum is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_promisc is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_switch_info is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_vf_mac_addr_modify is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_vlan_vmwa_create is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_nl_vlan_vmwa_delete is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol mlx5_translate_port_name is added in the DPDK_20.02 section, but is expected to be added in the EXPERIMENTAL section of the version map
parent reply other threads:[~2020-01-28 16:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1580228860-10665-25-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=20200128163407.E01FE1C1D3@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).