automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jia He <hejianet@gmail.com>
Subject: [dpdk-test-report] |WARNING| pw30332 [PATCH] ring: guarantee ordering of cons/prod loading when doing enqueue/dequeue
Date: Fri, 13 Oct 2017 05:24:32 +0200 (CEST)	[thread overview]
Message-ID: <20171013032432.8979C1B66F@dpdk.org> (raw)
In-Reply-To: <0c307108-be4f-42bf-f6a6-ac3099bf2985@gmail.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#28: 
>> Cc: Olivier MATZ <olivier.matz@6wind.com>, "dev@dpdk.org" <dev@dpdk.org>,

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#180: FILE: test/test/test_mbuf.c:87:
+int test_mbuf(void);

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#201: FILE: test/test/test_mbuf.c:749:
+			    __func__, lcore, iter, tref);*/

ERROR:CODE_INDENT: code indent should use tabs where possible
#207: FILE: test/test/test_mbuf.c:755:
+        rte_mempool_dump(stdout, refcnt_pool);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#207: FILE: test/test/test_mbuf.c:755:
+        rte_mempool_dump(stdout, refcnt_pool);$

ERROR:CODE_INDENT: code indent should use tabs where possible
#209: FILE: test/test/test_mbuf.c:757:
+        rte_ring_dump(stdout, refcnt_mbuf_ring);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#209: FILE: test/test/test_mbuf.c:757:
+        rte_ring_dump(stdout, refcnt_mbuf_ring);$

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

total: 3 errors, 5 warnings, 82 lines checked

           reply	other threads:[~2017-10-13  3:24 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <0c307108-be4f-42bf-f6a6-ac3099bf2985@gmail.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=20171013032432.8979C1B66F@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=hejianet@gmail.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).