automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jiayu Hu <jiayu.hu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw95589 [PATCH v3 3/3] vhost: add thread unsafe async registeration functions
Date: Fri,  9 Jul 2021 05:16:44 +0200 (CEST)	[thread overview]
Message-ID: <20210709031644.5117B120736@dpdk.org> (raw)
In-Reply-To: <1625823790-91995-4-git-send-email-jiayu.hu@intel.com>

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

_coding style issues_


WARNING:BRACES: braces {} are not necessary for single statement blocks
#270: FILE: lib/vhost/vhost.c:1713:
+	if (dev == NULL || ops == NULL) {
+		return -1;
+	}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#274: FILE: lib/vhost/vhost.c:1717:
+	if (queue_id >= VHOST_MAX_VRING) {
+		return -1;
+	}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#280: FILE: lib/vhost/vhost.c:1723:
+	if (unlikely(vq == NULL || !dev->async_copy)) {
+		return -1;
+	}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#311: FILE: lib/vhost/vhost.c:1753:
+	if (dev == NULL || ops == NULL) {
+		return -1;
+	}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#315: FILE: lib/vhost/vhost.c:1757:
+	if (queue_id >= VHOST_MAX_VRING) {
+		return -1;
+	}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#321: FILE: lib/vhost/vhost.c:1763:
+	if (unlikely(vq == NULL || !dev->async_copy)) {
+		return -1;
+	}

total: 0 errors, 6 warnings, 289 lines checked

           reply	other threads:[~2021-07-09  3:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1625823790-91995-4-git-send-email-jiayu.hu@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=20210709031644.5117B120736@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=jiayu.hu@intel.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).