From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shrikrishna Khare <skhare@vmware.com>
Subject: [dpdk-test-report] |WARNING| pw20790 [PATCH 2/7] vmxnet3: introduce generalized command interface to configure the device
Date: Sat, 25 Feb 2017 23:00:54 +0100 (CET) [thread overview]
Message-ID: <20170225220054.82107F60E@dpdk.org> (raw)
In-Reply-To: <1488059989-6930-3-git-send-email-skhare@vmware.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/20790
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#58:
on the type of the command. This patch exposes this capability to the driver.
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#75: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:112:
+ VMXNET3_CMD_RESERVED3,$
CHECK:CAMELCASE: Avoid CamelCase: <Vmxnet3_SetPolling>
#83: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:699:
+struct Vmxnet3_SetPolling {
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#84: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:700:
+ uint8 enablePolling;$
CHECK:CAMELCASE: Avoid CamelCase: <enablePolling>
#84: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:700:
+ uint8 enablePolling;
CHECK:CAMELCASE: Avoid CamelCase: <Vmxnet3_CmdInfo>
#95: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:711:
+union Vmxnet3_CmdInfo {
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#96: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:712:
+ Vmxnet3_VariableLenConfDesc varConf;$
CHECK:CAMELCASE: Avoid CamelCase: <Vmxnet3_VariableLenConfDesc>
#96: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:712:
+ Vmxnet3_VariableLenConfDesc varConf;
CHECK:CAMELCASE: Avoid CamelCase: <varConf>
#96: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:712:
+ Vmxnet3_VariableLenConfDesc varConf;
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#97: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:713:
+ Vmxnet3_SetPolling setPolling;$
CHECK:CAMELCASE: Avoid CamelCase: <setPolling>
#97: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:713:
+ Vmxnet3_SetPolling setPolling;
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#98: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:714:
+ __le64 data[2];$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#111: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:726:
+ __le32 reserved;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#113: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:728:
+ union {$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#114: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:729:
+ __le32 reserved1[4];$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#115: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:730:
+ Vmxnet3_CmdInfo cmdInfo; /* only valid in the context of executing the$
CHECK:CAMELCASE: Avoid CamelCase: <cmdInfo>
#115: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:730:
+ Vmxnet3_CmdInfo cmdInfo; /* only valid in the context of executing the
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#118: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:733:
+ } cu;$
total: 0 errors, 11 warnings, 7 checks, 49 lines checked
parent reply other threads:[~2017-02-25 22:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1488059989-6930-3-git-send-email-skhare@vmware.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=20170225220054.82107F60E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=skhare@vmware.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).