automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-test-report] |WARNING| pw24214 [PATCH 6/6] eal: fix warning seen with armv8a clang
Date: Thu, 11 May 2017 07:54:53 +0200 (CEST)	[thread overview]
Message-ID: <20170511055453.661795A8D@dpdk.org> (raw)
In-Reply-To: <20170511055239.GF3057@jerin>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#35: 
> diff --git a/lib/librte_eal/linuxapp/eal/Makefile b/lib/librte_eal/linuxapp/eal/Makefile

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (7, 15)
#69: FILE: lib/librte_eal/common/eal_common_launch.c:56:
        while (lcore_config[slave_id].state != WAIT &&
[...]
+               rte_pause();

ERROR:CODE_INDENT: code indent should use tabs where possible
#71: FILE: lib/librte_eal/common/eal_common_launch.c:57:
+              lcore_config[slave_id].state != FINISHED)$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#71: FILE: lib/librte_eal/common/eal_common_launch.c:57:
+              lcore_config[slave_id].state != FINISHED)$

ERROR:CODE_INDENT: code indent should use tabs where possible
#72: FILE: lib/librte_eal/common/eal_common_launch.c:58:
+               rte_pause();$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#72: FILE: lib/librte_eal/common/eal_common_launch.c:58:
+               rte_pause();$

ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)

total: 3 errors, 4 warnings, 9 lines checked

           reply	other threads:[~2017-05-11  5:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20170511055239.GF3057@jerin>]

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=20170511055453.661795A8D@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.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).