From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrew Rybchenko <arybchenko@solarflare.com>
Subject: [dpdk-test-report] |WARNING| pw36967 [PATCH 1/5] net/sfc/base: update MCDI headers
Date: Tue, 3 Apr 2018 17:09:21 +0200 (CEST) [thread overview]
Message-ID: <20180403150921.AD3741B7EA@dpdk.org> (raw)
In-Reply-To: <1522768027-17384-2-git-send-email-arybchenko@solarflare.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/36967
_coding style issues_
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#29: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:284:
+ * May also returned for other operations such as sub-variant switching. */
CHECK:SPACING: spaces preferred around that '+' (ctx:VxV)
#4842: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:15615:
+#define MC_CMD_TSA_BIND_IN_SECURE_UNBIND_LEN(num) (96+1*(num))
^
CHECK:SPACING: spaces preferred around that '*' (ctx:VxV)
#4842: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:15615:
+#define MC_CMD_TSA_BIND_IN_SECURE_UNBIND_LEN(num) (96+1*(num))
^
CHECK:SPACING: spaces preferred around that '+' (ctx:VxV)
#4883: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:15656:
+#define MC_CMD_TSA_BIND_IN_SECURE_DECOMMISSION_LEN(num) (112+1*(num))
^
CHECK:SPACING: spaces preferred around that '*' (ctx:VxV)
#4883: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:15656:
+#define MC_CMD_TSA_BIND_IN_SECURE_DECOMMISSION_LEN(num) (112+1*(num))
^
CHECK:SPACING: spaces preferred around that '+' (ctx:VxV)
#5640: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:17434:
+#define MC_CMD_GET_CERTIFICATE_OUT_LEN(num) (12+1*(num))
^
CHECK:SPACING: spaces preferred around that '*' (ctx:VxV)
#5640: FILE: drivers/net/sfc/base/efx_regs_mcdi.h:17434:
+#define MC_CMD_GET_CERTIFICATE_OUT_LEN(num) (12+1*(num))
^
total: 0 errors, 1 warnings, 6 checks, 5890 lines checked
parent reply other threads:[~2018-04-03 15:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1522768027-17384-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=20180403150921.AD3741B7EA@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).