automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Xiaolong Ye <xiaolong.ye@intel.com>
Subject: [dpdk-test-report] |WARNING| pw63491 [PATCH 63/69] net/i40e/base: update the interrupt mapping and negotiation
Date: Mon,  2 Dec 2019 09:09:22 +0100 (CET)	[thread overview]
Message-ID: <20191202080922.ED38F1C1CE@dpdk.org> (raw)
In-Reply-To: <20191202074935.97629-64-xiaolong.ye@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/63491

_coding style issues_


WARNING:LEADING_SPACE: please, no spaces at the start of a line
#79: FILE: drivers/net/i40e/base/virtchnl.h:159:
+       VIRTCHNL_OP_MAP_QUEUE_VECTOR = 111,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#80: FILE: drivers/net/i40e/base/virtchnl.h:160:
+       VIRTCHNL_OP_UNMAP_QUEUE_VECTOR = 112,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#81: FILE: drivers/net/i40e/base/virtchnl.h:161:
+       VIRTCHNL_OP_GET_RSS_KEY = 113,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#82: FILE: drivers/net/i40e/base/virtchnl.h:162:
+       VIRTCHNL_OP_GET_RSS_LUT = 114,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#83: FILE: drivers/net/i40e/base/virtchnl.h:163:
+       VIRTCHNL_OP_SET_RSS_LUT = 115,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#88: FILE: drivers/net/i40e/base/virtchnl.h:168:
+       VIRTCHNL_OP_ALLOC_VECTORS = 120,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#89: FILE: drivers/net/i40e/base/virtchnl.h:169:
+       VIRTCHNL_OP_DEALLOC_VECTORS = 121,$

total: 0 errors, 7 warnings, 0 checks, 240 lines checked

           reply	other threads:[~2019-12-02  8:09 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20191202074935.97629-64-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=20191202080922.ED38F1C1CE@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).