From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Subject: [dpdk-test-report] |WARNING| pw23680 [PATCH v3 1/3] test/test/mempool_perf: Remove mempool global vars
Date: Tue, 18 Apr 2017 10:36:26 +0200 (CEST) [thread overview]
Message-ID: <20170418083626.67C6D2C6E@dpdk.org> (raw)
In-Reply-To: <20170418083448.24743-1-santosh.shukla@caviumnetworks.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/23680
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#57: FILE: test/test/test_mempool_perf.c:223:
+launch_cores(struct rte_mempool *mp, unsigned cores)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#82: FILE: test/test/test_mempool_perf.c:284:
+do_one_mempool_test(struct rte_mempool *mp, unsigned cores)
total: 0 errors, 2 warnings, 148 lines checked
parent reply other threads:[~2017-04-18 8:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170418083448.24743-1-santosh.shukla@caviumnetworks.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=20170418083626.67C6D2C6E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=santosh.shukla@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).