automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jens Freimann <jfreimann@redhat.com>
Subject: [dpdk-test-report] |WARNING| pw37266 [PATCH v3 05/21] net/virtio: dump packed virtqueue data
Date: Thu,  5 Apr 2018 12:11:21 +0200 (CEST)	[thread overview]
Message-ID: <20180405101121.CEA9E1CAC0@dpdk.org> (raw)
In-Reply-To: <20180405101031.26468-6-jfreimann@redhat.com>

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

_coding style issues_


WARNING:LEADING_SPACE: please, no spaces at the start of a line
#31: FILE: drivers/net/virtio/virtqueue.h:363:
+       if (vtpci_packed_queue((vq)->hw)) { \$

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (7, 9)
#31: FILE: drivers/net/virtio/virtqueue.h:363:
+       if (vtpci_packed_queue((vq)->hw)) { \
+         PMD_INIT_LOG(DEBUG, \

ERROR:CODE_INDENT: code indent should use tabs where possible
#32: FILE: drivers/net/virtio/virtqueue.h:364:
+         PMD_INIT_LOG(DEBUG, \$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#32: FILE: drivers/net/virtio/virtqueue.h:364:
+         PMD_INIT_LOG(DEBUG, \$

ERROR:CODE_INDENT: code indent should use tabs where possible
#33: FILE: drivers/net/virtio/virtqueue.h:365:
+         "VQ: - size=%d; free=%d; last_used_idx=%d;" \$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#33: FILE: drivers/net/virtio/virtqueue.h:365:
+         "VQ: - size=%d; free=%d; last_used_idx=%d;" \$

ERROR:CODE_INDENT: code indent should use tabs where possible
#34: FILE: drivers/net/virtio/virtqueue.h:366:
+         (vq)->vq_nentries, (vq)->vq_free_cnt, nused); \$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#34: FILE: drivers/net/virtio/virtqueue.h:366:
+         (vq)->vq_nentries, (vq)->vq_free_cnt, nused); \$

ERROR:CODE_INDENT: code indent should use tabs where possible
#35: FILE: drivers/net/virtio/virtqueue.h:367:
+         break; \$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#35: FILE: drivers/net/virtio/virtqueue.h:367:
+         break; \$

ERROR:CODE_INDENT: code indent should use tabs where possible
#36: FILE: drivers/net/virtio/virtqueue.h:368:
+         } \$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#36: FILE: drivers/net/virtio/virtqueue.h:368:
+         } \$

ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#37: FILE: drivers/net/virtio/virtqueue.h:369:
+	if (vtpci_packed_queue((vq)->hw)) break; \

total: 6 errors, 7 warnings, 0 checks, 13 lines checked

           reply	other threads:[~2018-04-05 10:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20180405101031.26468-6-jfreimann@redhat.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=20180405101121.CEA9E1CAC0@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=jfreimann@redhat.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).