automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Agota Benyhe <agota.benyhe@ericsson.com>
Subject: [dpdk-test-report] |WARNING| pw31925 [PATCH] virtio_net: kick guest even when virtio queue is full
Date: Tue,  5 Dec 2017 10:08:14 +0100 (CET)	[thread overview]
Message-ID: <20171205090814.F099E7CEA@dpdk.org> (raw)
In-Reply-To: <1512464838-17300-1-git-send-email-agota.benyhe@ericsson.com>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#62: FILE: lib/librte_vhost/virtio_net.c:356:
+                kick_guest_if_necessary(vq);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#62: FILE: lib/librte_vhost/virtio_net.c:356:
+                kick_guest_if_necessary(vq);$

ERROR:CODE_INDENT: code indent should use tabs where possible
#64: FILE: lib/librte_vhost/virtio_net.c:358:
+        }$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#64: FILE: lib/librte_vhost/virtio_net.c:358:
+        }$

ERROR:CODE_INDENT: code indent should use tabs where possible
#76: FILE: lib/librte_vhost/virtio_net.c:424:
+        kick_guest_if_necessary(vq);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#76: FILE: lib/librte_vhost/virtio_net.c:424:
+        kick_guest_if_necessary(vq);$

ERROR:CODE_INDENT: code indent should use tabs where possible
#91: FILE: lib/librte_vhost/virtio_net.c:716:
+        kick_guest_if_necessary(vq);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#91: FILE: lib/librte_vhost/virtio_net.c:716:
+        kick_guest_if_necessary(vq);$

total: 4 errors, 4 warnings, 50 lines checked

           reply	other threads:[~2017-12-05  9:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1512464838-17300-1-git-send-email-agota.benyhe@ericsson.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=20171205090814.F099E7CEA@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=agota.benyhe@ericsson.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).