From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shrikrishna Khare <skhare@vmware.com>
Subject: [dpdk-test-report] |WARNING| pw21522 [PATCH v3 4/7] net/vmxnet3: add receive data ring support
Date: Mon, 6 Mar 2017 23:55:36 +0100 (CET) [thread overview]
Message-ID: <20170306225536.7B58C6CB4@dpdk.org> (raw)
In-Reply-To: <1488840907-17441-5-git-send-email-skhare@vmware.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/21522
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#95: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:538:
+ __le64 rxDataRingBasePA;$
CHECK:CAMELCASE: Avoid CamelCase: <rxDataRingBasePA>
#95: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:538:
+ __le64 rxDataRingBasePA;
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#101: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:543:
+ uint8 _pad1[1];$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#102: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:544:
+ __le16 rxDataRingDescSize; /* size of rx data ring buffer */$
CHECK:CAMELCASE: Avoid CamelCase: <rxDataRingDescSize>
#102: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:544:
+ __le16 rxDataRingDescSize; /* size of rx data ring buffer */
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#103: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:545:
+ uint8 _pad2[4];$
CHECK:CAMELCASE: Avoid CamelCase: <basePA>
#128: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:560:
+ rqd->conf.rxDataRingBasePA = rxq->data_ring.basePA;
CHECK:CAMELCASE: Avoid CamelCase: <rqID>
#151: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.h:162:
+vmxnet3_get_ring_idx(struct vmxnet3_hw *hw, uint32 rqID)
CHECK:CAMELCASE: Avoid CamelCase: <Vmxnet3_RxCompDesc>
#303: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:1120:
+ sizeof(struct Vmxnet3_RxCompDesc) * comp_ring->size;
total: 0 errors, 4 warnings, 5 checks, 205 lines checked
parent reply other threads:[~2017-03-06 22:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1488840907-17441-5-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=20170306225536.7B58C6CB4@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).