automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: wangzhike <wangzhike@jd.com>
Subject: [dpdk-test-report] |WARNING| pw32770 [PATCH] lib/librte_vhost: move fdset_del out of conn_mutex
Date: Wed, 27 Dec 2017 14:11:45 +0100 (CET)	[thread overview]
Message-ID: <20171227131145.902DB1B2A5@dpdk.org> (raw)
In-Reply-To: <1514380252-91162-1-git-send-email-wangzhike@jd.com>

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

_coding style issues_


ERROR:SPACING: spaces required around that '=' (ctx:VxV)
#59: FILE: lib/librte_vhost/socket.c:784:
+			for(i=0;i<num_of_fds;i++){
 			     ^

ERROR:SPACING: space required after that ';' (ctx:VxV)
#59: FILE: lib/librte_vhost/socket.c:784:
+			for(i=0;i<num_of_fds;i++){
 			       ^

ERROR:SPACING: spaces required around that '<' (ctx:VxV)
#59: FILE: lib/librte_vhost/socket.c:784:
+			for(i=0;i<num_of_fds;i++){
 			         ^

ERROR:SPACING: space required after that ';' (ctx:VxV)
#59: FILE: lib/librte_vhost/socket.c:784:
+			for(i=0;i<num_of_fds;i++){
 			                    ^

ERROR:SPACING: space required before the open brace '{'
#59: FILE: lib/librte_vhost/socket.c:784:
+			for(i=0;i<num_of_fds;i++){

ERROR:SPACING: space required before the open parenthesis '('
#59: FILE: lib/librte_vhost/socket.c:784:
+			for(i=0;i<num_of_fds;i++){

WARNING:BRACES: braces {} are not necessary for single statement blocks
#59: FILE: lib/librte_vhost/socket.c:784:
+			for(i=0;i<num_of_fds;i++){
+				fdset_del(&vhost_user.fdset, del_fds[i]);
+			}

total: 6 errors, 1 warnings, 27 lines checked

           reply	other threads:[~2017-12-27 13:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1514380252-91162-1-git-send-email-wangzhike@jd.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=20171227131145.902DB1B2A5@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=wangzhike@jd.com \
    /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).