automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Subject: [dpdk-test-report] |WARNING| pw34111 [PATCH RFC 17/24] vhost: add virtio-vhost-user transport
Date: Fri, 19 Jan 2018 14:48:02 +0100 (CET)	[thread overview]
Message-ID: <20180119134802.D4BC71B36B@dpdk.org> (raw)
In-Reply-To: <20180119134444.24927-18-stefanha@redhat.com>

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

_coding style issues_


WARNING:LEADING_SPACE: please, no spaces at the start of a line
#80: FILE: drivers/librte_vhost/virtio_vhost_user.h:11:
+    uint32_t status;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#83: FILE: drivers/librte_vhost/virtio_vhost_user.h:14:
+    uint32_t max_vhost_queues;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#84: FILE: drivers/librte_vhost/virtio_vhost_user.h:15:
+    uint8_t uuid[16];$

WARNING:RETURN_VOID: void function return statements are not generally useful
#430: FILE: drivers/librte_vhost/trans_virtio_vhost_user.c:337:
+	return;
+}

WARNING:LONG_LINE: line over 90 characters
#559: FILE: drivers/librte_vhost/trans_virtio_vhost_user.c:466:
+		RTE_LOG(DEBUG, VHOST_CONFIG, "%s isr %#x status %#x
", __func__, isr, status);

ERROR:CODE_INDENT: code indent should use tabs where possible
#604: FILE: drivers/librte_vhost/trans_virtio_vhost_user.c:511:
+^I^I^I^I              i * VVU_RXBUF_SIZE);$

WARNING:TYPO_SPELLING: 'availabled' may be misspelled - perhaps 'available'?
#864: FILE: drivers/librte_vhost/trans_virtio_vhost_user.c:771:
+		RTE_LOG(ERR, VHOST_CONFIG, "BAR 2 not availabled
");

total: 1 errors, 6 warnings, 1084 lines checked

           reply	other threads:[~2018-01-19 13:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20180119134444.24927-18-stefanha@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=20180119134802.D4BC71B36B@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=stefanha@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).