From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrew Rybchenko <arybchenko@solarflare.com>
Subject: [dpdk-test-report] |WARNING| pw38524 [PATCH 01/23] net/sfc/base: update autogenerated MCDI and TLV headers
Date: Thu, 19 Apr 2018 13:37:52 +0200 (CEST) [thread overview]
Message-ID: <20180419113752.C243FEE2D@dpdk.org> (raw)
In-Reply-To: <1524137826-5675-2-git-send-email-arybchenko@solarflare.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/38524
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#61: FILE: drivers/net/sfc/base/ef10_tlv_layout.h:1005:
+ uint32_t tag;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#62: FILE: drivers/net/sfc/base/ef10_tlv_layout.h:1006:
+ uint32_t length;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#63: FILE: drivers/net/sfc/base/ef10_tlv_layout.h:1007:
+ uint16_t ports[];$
CHECK:SPACING: spaces preferred around that '*' (ctx:VxV)
#278: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:4380:
+#define MC_CMD_MAC_STATS_V4_OUT_NO_DMA_LEN (((MC_CMD_MAC_NSTATS_V4*64))>>3)
^
CHECK:SPACING: spaces preferred around that '>>' (ctx:VxV)
#278: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:4380:
+#define MC_CMD_MAC_STATS_V4_OUT_NO_DMA_LEN (((MC_CMD_MAC_NSTATS_V4*64))>>3)
^
WARNING:LONG_LINE: line over 90 characters
#472: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:11078:
+#define MC_CMD_GET_CAPABILITIES_V5_OUT_UNKNOWN_UCAST_DST_FILTER_ALWAYS_MULTI_RECIPIENT_LBN 10
WARNING:LONG_LINE: line over 90 characters
#473: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:11079:
+#define MC_CMD_GET_CAPABILITIES_V5_OUT_UNKNOWN_UCAST_DST_FILTER_ALWAYS_MULTI_RECIPIENT_WIDTH 1
WARNING:LONG_LINE: line over 90 characters
#474: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:11080:
+#define MC_CMD_GET_CAPABILITIES_V5_OUT_VADAPTOR_PERMIT_SET_MAC_WHEN_FILTERS_INSTALLED_LBN 11
WARNING:LONG_LINE: line over 90 characters
#475: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:11081:
+#define MC_CMD_GET_CAPABILITIES_V5_OUT_VADAPTOR_PERMIT_SET_MAC_WHEN_FILTERS_INSTALLED_WIDTH 1
CHECK:SPACING: spaces preferred around that '+' (ctx:VxV)
#862: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:18109:
+#define MC_CMD_LTSSM_TRACE_POLL_OUT_LEN(num) (8+8*(num))
^
CHECK:SPACING: spaces preferred around that '*' (ctx:VxV)
#862: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:18109:
+#define MC_CMD_LTSSM_TRACE_POLL_OUT_LEN(num) (8+8*(num))
^
total: 0 errors, 7 warnings, 4 checks, 843 lines checked
parent reply other threads:[~2018-04-19 11:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1524137826-5675-2-git-send-email-arybchenko@solarflare.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=20180419113752.C243FEE2D@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=arybchenko@solarflare.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).