From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ronak Doshi <doshir@vmware.com>
Subject: |WARNING| pw126161 [PATCH next 4/7] vmxnet3: add command to set ring buffer sizes
Date: Mon, 17 Apr 2023 10:16:22 +0200 (CEST) [thread overview]
Message-ID: <20230417081622.4EC87121EF4@dpdk.org> (raw)
In-Reply-To: <20230412162636.30843-5-doshir@vmware.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/126161
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#80: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:108:
+ VMXNET3_CMD_RESERVED9,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#81: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:109:
+ VMXNET3_CMD_RESERVED10,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#82: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:110:
+ VMXNET3_CMD_SET_RING_BUFFER_SIZE,$
CHECK:CAMELCASE: Avoid CamelCase: <Vmxnet3_RingBufferSize>
#92: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:830:
+struct Vmxnet3_RingBufferSize {
CHECK:CAMELCASE: Avoid CamelCase: <ring1BufSizeType0>
#93: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:831:
+ __le16 ring1BufSizeType0;
CHECK:CAMELCASE: Avoid CamelCase: <ring1BufSizeType1>
#94: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:832:
+ __le16 ring1BufSizeType1;
CHECK:CAMELCASE: Avoid CamelCase: <ring2BufSizeType1>
#95: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:833:
+ __le16 ring2BufSizeType1;
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#108: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:849:
+ Vmxnet3_RingBufferSize ringBufSize;$
CHECK:CAMELCASE: Avoid CamelCase: <ringBufSize>
#108: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:849:
+ Vmxnet3_RingBufferSize ringBufSize;
CHECK:CAMELCASE: Avoid CamelCase: <cmdInfo>
#124: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:1025:
+ union Vmxnet3_CmdInfo *cmd_info = &shared->cu.cmdInfo;
total: 0 errors, 4 warnings, 6 checks, 95 lines checked
parent reply other threads:[~2023-04-17 8:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230412162636.30843-5-doshir@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=20230417081622.4EC87121EF4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=doshir@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).