From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Xiaolong Ye <xiaolong.ye@intel.com>
Subject: [dpdk-test-report] |WARNING| pw63483 [PATCH 57/69] net/i40e/base: update virtchnl header with advanced features
Date: Mon, 2 Dec 2019 09:07:32 +0100 (CET) [thread overview]
Message-ID: <20191202080732.A88161C1F2@dpdk.org> (raw)
In-Reply-To: <20191202074935.97629-58-xiaolong.ye@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/63483
_coding style issues_
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#78: FILE: drivers/net/i40e/base/virtchnl.h:139:
+ /* New major set of opcodes introduced and so leaving room for
+ * old misc opcodes to be added in future. Also these opcodes may only
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#83: FILE: drivers/net/i40e/base/virtchnl.h:144:
+ VIRTCHNL_OP_GET_CAPS = 100,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#84: FILE: drivers/net/i40e/base/virtchnl.h:145:
+ VIRTCHNL_OP_CREATE_VPORT = 101,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#85: FILE: drivers/net/i40e/base/virtchnl.h:146:
+ VIRTCHNL_OP_DESTROY_VPORT = 102,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#86: FILE: drivers/net/i40e/base/virtchnl.h:147:
+ VIRTCHNL_OP_ENABLE_VPORT = 103,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#87: FILE: drivers/net/i40e/base/virtchnl.h:148:
+ VIRTCHNL_OP_DISABLE_VPORT = 104,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#88: FILE: drivers/net/i40e/base/virtchnl.h:149:
+ VIRTCHNL_OP_CONFIG_TX_QUEUES = 105,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#89: FILE: drivers/net/i40e/base/virtchnl.h:150:
+ VIRTCHNL_OP_CONFIG_RX_QUEUES = 106,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#90: FILE: drivers/net/i40e/base/virtchnl.h:151:
+ VIRTCHNL_OP_ENABLE_QUEUES_V2 = 107,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#91: FILE: drivers/net/i40e/base/virtchnl.h:152:
+ VIRTCHNL_OP_DISABLE_QUEUES_V2 = 108,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#92: FILE: drivers/net/i40e/base/virtchnl.h:153:
+ VIRTCHNL_OP_ADD_QUEUES = 109,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#93: FILE: drivers/net/i40e/base/virtchnl.h:154:
+ VIRTCHNL_OP_DEL_QUEUES = 110,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#94: FILE: drivers/net/i40e/base/virtchnl.h:155:
+ VIRTCHNL_OP_MAP_VECTOR_QUEUE = 111,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#95: FILE: drivers/net/i40e/base/virtchnl.h:156:
+ VIRTCHNL_OP_UNMAP_VECTOR_QUEUE = 112,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#96: FILE: drivers/net/i40e/base/virtchnl.h:157:
+ VIRTCHNL_OP_MAP_VECTOR_ITR = 113,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#97: FILE: drivers/net/i40e/base/virtchnl.h:158:
+ VIRTCHNL_OP_GET_RSS_KEY = 114,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#98: FILE: drivers/net/i40e/base/virtchnl.h:159:
+ VIRTCHNL_OP_GET_RSS_LUT = 115,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#99: FILE: drivers/net/i40e/base/virtchnl.h:160:
+ VIRTCHNL_OP_GET_RSS_HASH = 116,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#100: FILE: drivers/net/i40e/base/virtchnl.h:161:
+ VIRTCHNL_OP_SET_RSS_HASH = 117,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#101: FILE: drivers/net/i40e/base/virtchnl.h:162:
+ VIRTCHNL_OP_CREATE_VFS = 118,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#102: FILE: drivers/net/i40e/base/virtchnl.h:163:
+ VIRTCHNL_OP_DESTROY_VFS = 119,$
total: 0 errors, 21 warnings, 0 checks, 536 lines checked
parent reply other threads:[~2019-12-02 8:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20191202074935.97629-58-xiaolong.ye@intel.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=20191202080732.A88161C1F2@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=xiaolong.ye@intel.com \
/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).