From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ronak Doshi <doshir@vmware.com>
Subject: |WARNING| pw126552 [PATCH v2 next 2/7] net/vmxnet3: add support for capability registers
Date: Wed, 26 Apr 2023 21:32:29 +0200 (CEST) [thread overview]
Message-ID: <20230426193229.1CAFF121EF6@dpdk.org> (raw)
In-Reply-To: <20230426190415.28239-3-doshir@vmware.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/126552
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#105: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:112:
+ VMXNET3_CMD_RESERVED5,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#106: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:113:
+ VMXNET3_CMD_RESERVED6,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#107: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:114:
+ VMXNET3_CMD_RESERVED7,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#108: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:115:
+ VMXNET3_CMD_RESERVED8,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#109: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:116:
+ VMXNET3_CMD_GET_MAX_QUEUES_CONF,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#110: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:117:
+ VMXNET3_CMD_GET_MAX_CAPABILITIES,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#111: FILE: drivers/net/vmxnet3/base/vmxnet3_defs.h:118:
+ VMXNET3_CMD_GET_DCR0_REG,$
total: 0 errors, 7 warnings, 0 checks, 149 lines checked
parent reply other threads:[~2023-04-26 19:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230426190415.28239-3-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=20230426193229.1CAFF121EF6@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).