automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jens Freimann <jfreiman@redhat.com>
Subject: [dpdk-test-report] |WARNING| pw24130 [PATCH RFC 06/11] vhost: implement virtio 1.1 dequeue path
Date: Fri,  5 May 2017 15:58:40 +0200 (CEST)	[thread overview]
Message-ID: <20170505135840.DF87E68C1@dpdk.org> (raw)
In-Reply-To: <1493992642-52756-7-git-send-email-jfreiman@redhat.com>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#48: FILE: lib/librte_vhost/virtio-1.1.h:17:
+        __le64 addr;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#48: FILE: lib/librte_vhost/virtio-1.1.h:17:
+        __le64 addr;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#49: FILE: lib/librte_vhost/virtio-1.1.h:18:
+        __le32 len;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#49: FILE: lib/librte_vhost/virtio-1.1.h:18:
+        __le32 len;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#50: FILE: lib/librte_vhost/virtio-1.1.h:19:
+        __le16 index;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#50: FILE: lib/librte_vhost/virtio-1.1.h:19:
+        __le16 index;$

ERROR:CODE_INDENT: code indent should use tabs where possible
#51: FILE: lib/librte_vhost/virtio-1.1.h:20:
+        __le16 flags;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#51: FILE: lib/librte_vhost/virtio-1.1.h:20:
+        __le16 flags;$

ERROR:ASSIGN_IN_IF: do not use assignment in if condition
#139: FILE: lib/librte_vhost/virtio_net.c:1045:
+		if (unlikely(dev->dequeue_zero_copy && (hpa = gpa_to_hpa(dev,

total: 5 errors, 4 warnings, 222 lines checked

           reply	other threads:[~2017-05-05 13:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1493992642-52756-7-git-send-email-jfreiman@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=20170505135840.DF87E68C1@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=jfreiman@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).