From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shrikrishna Khare <skhare@vmware.com>
Subject: [dpdk-test-report] |WARNING| pw20789 [PATCH 3/7] vmxnet3: allow variable length transmit data ring buffer
Date: Sat, 25 Feb 2017 23:00:50 +0100 (CET) [thread overview]
Message-ID: <20170225220050.3E021D4A4@dpdk.org> (raw)
In-Reply-To: <1488059989-6930-4-git-send-email-skhare@vmware.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/20789
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#75: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:124:
+ VMXNET3_CMD_GET_ADAPTIVE_RING_INFO,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#76: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:125:
+ VMXNET3_CMD_GET_TXDATA_DESC_SIZE$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#105: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:519:
+ uint8 _pad[1];$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#106: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:520:
+ __le16 txDataRingDescSize;$
CHECK:CAMELCASE: Avoid CamelCase: <txDataRingDescSize>
#106: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:520:
+ __le16 txDataRingDescSize;
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#107: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:521:
+ uint8 _pad2[4];$
CHECK:CAMELCASE: Avoid CamelCase: <Vmxnet3_TxDataDesc>
#133: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:242:
+ sizeof(struct Vmxnet3_TxDataDesc) : txdata_desc_size;
total: 0 errors, 5 warnings, 2 checks, 139 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-4-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=20170225220050.3E021D4A4@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).