From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw22487 [PATCH 28/28] bnxt: update to HWRM version 1.7.4
Date: Tue, 28 Mar 2017 14:27:01 +0200 (CEST) [thread overview]
Message-ID: <20170328122701.767DDCFA6@dpdk.org> (raw)
In-Reply-To: <20170328034903.41482-29-ajit.khaparde@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/22487
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#2796: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:2578:
+ #define HWRM_FUNC_CFG_INPUT_MIN_BW_BW_VALUE_UNIT_INVALID (UINT32_C(0x7) << 29)
WARNING:LONG_LINE: line over 90 characters
#2850: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:2614:
+ #define HWRM_FUNC_CFG_INPUT_MAX_BW_BW_VALUE_UNIT_INVALID (UINT32_C(0x7) << 29)
WARNING:LONG_LINE: line over 90 characters
#5750: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5988:
+ #define HWRM_RING_ALLOC_INPUT_RING_ARB_CFG_ARB_POLICY_SP (UINT32_C(0x1) << 0)
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'x' - possible side-effects?
#6815: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7804:
+#define HWRM_GET_HWRM_ERROR_CODE(x) \
+ ((x) == 0xf ? "HWRM_ERROR": \
+ ((x) == 0xffff ? "CMD_NOT_SUPPORTED": \
+ ((x) == 0xfffe ? "UNKNOWN_ERR": \
+ ((x) == 0x4 ? "RESOURCE_ALLOC_ERROR": \
+ ((x) == 0x5 ? "INVALID_FLAGS": \
+ ((x) == 0x6 ? "INVALID_ENABLES": \
+ ((x) == 0x0 ? "SUCCESS": \
+ ((x) == 0x1 ? "FAIL": \
+ ((x) == 0x2 ? "INVALID_PARAMS": \
+ ((x) == 0x3 ? "RESOURCE_ACCESS_DENIED": \
+ "Unknown error_code"))))))))))
ERROR:SPACING: spaces required around that ':' (ctx:VxE)
#6816: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7805:
+ ((x) == 0xf ? "HWRM_ERROR": \
^
ERROR:SPACING: spaces required around that ':' (ctx:VxE)
#6817: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7806:
+ ((x) == 0xffff ? "CMD_NOT_SUPPORTED": \
^
ERROR:SPACING: spaces required around that ':' (ctx:VxE)
#6818: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7807:
+ ((x) == 0xfffe ? "UNKNOWN_ERR": \
^
ERROR:SPACING: spaces required around that ':' (ctx:VxE)
#6819: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7808:
+ ((x) == 0x4 ? "RESOURCE_ALLOC_ERROR": \
^
ERROR:SPACING: spaces required around that ':' (ctx:VxE)
#6820: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7809:
+ ((x) == 0x5 ? "INVALID_FLAGS": \
^
ERROR:SPACING: spaces required around that ':' (ctx:VxE)
#6821: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7810:
+ ((x) == 0x6 ? "INVALID_ENABLES": \
^
ERROR:SPACING: spaces required around that ':' (ctx:VxE)
#6822: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7811:
+ ((x) == 0x0 ? "SUCCESS": \
^
ERROR:SPACING: spaces required around that ':' (ctx:VxE)
#6823: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7812:
+ ((x) == 0x1 ? "FAIL": \
^
ERROR:SPACING: spaces required around that ':' (ctx:VxE)
#6824: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7813:
+ ((x) == 0x2 ? "INVALID_PARAMS": \
^
ERROR:SPACING: spaces required around that ':' (ctx:VxE)
#6825: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7814:
+ ((x) == 0x3 ? "RESOURCE_ACCESS_DENIED": \
^
total: 10 errors, 3 warnings, 1 checks, 7065 lines checked
parent reply other threads:[~2017-03-28 12:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170328034903.41482-29-ajit.khaparde@broadcom.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=20170328122701.767DDCFA6@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ajit.khaparde@broadcom.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).