From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harry van Haaren <harry.van.haaren@intel.com>
Subject: [dpdk-test-report] |WARNING| pw23799 [PATCH 1/3] examples/eventdev_pipeline: added sample app
Date: Fri, 21 Apr 2017 11:54:02 +0200 (CEST) [thread overview]
Message-ID: <20170421095402.63DD82C72@dpdk.org> (raw)
In-Reply-To: <1492768299-84016-2-git-send-email-harry.van.haaren@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/23799
_coding style issues_
WARNING:TYPO_SPELLING: 'recieves' may be misspelled - perhaps 'receives'?
#24:
The application recieves traffic as normal, with each
WARNING:TYPO_SPELLING: 'overriden' may be misspelled - perhaps 'overridden'?
#89: FILE: examples/eventdev_pipeline/Makefile:35:
+# Default target, can be overriden by command line or environment
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#180: FILE: examples/eventdev_pipeline/main.c:71:
+ unsigned num_nic_ports;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int *' to bare use of 'unsigned *'
#196: FILE: examples/eventdev_pipeline/main.c:87:
+static unsigned *enqueue_cnt;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int *' to bare use of 'unsigned *'
#197: FILE: examples/eventdev_pipeline/main.c:88:
+static unsigned *dequeue_cnt;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#212: FILE: examples/eventdev_pipeline/main.c:103:
+static unsigned rx_core[MAX_NUM_CORE];
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#213: FILE: examples/eventdev_pipeline/main.c:104:
+static unsigned tx_core[MAX_NUM_CORE];
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#214: FILE: examples/eventdev_pipeline/main.c:105:
+static unsigned sched_core[MAX_NUM_CORE];
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#215: FILE: examples/eventdev_pipeline/main.c:106:
+static unsigned worker_core[MAX_NUM_CORE];
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#218: FILE: examples/eventdev_pipeline/main.c:109:
+core_in_use(unsigned lcore_id) {
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#230: FILE: examples/eventdev_pipeline/main.c:121:
+ unsigned _sent = 0;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#250: FILE: examples/eventdev_pipeline/main.c:141:
+ unsigned i, j;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#351: FILE: examples/eventdev_pipeline/main.c:242:
+schedule_devices(uint8_t dev_id, unsigned lcore_id)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#385: FILE: examples/eventdev_pipeline/main.c:276:
+ unsigned lcore_id = rte_lcore_id();
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#467: FILE: examples/eventdev_pipeline/main.c:358:
+ unsigned count = 0;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#715: FILE: examples/eventdev_pipeline/main.c:606:
+ (unsigned)port,
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#727: FILE: examples/eventdev_pipeline/main.c:618:
+init_ports(unsigned num_ports)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#730: FILE: examples/eventdev_pipeline/main.c:621:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#808: FILE: examples/eventdev_pipeline/main.c:699:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#951: FILE: examples/eventdev_pipeline/main.c:842:
+ unsigned num_ports;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#973: FILE: examples/eventdev_pipeline/main.c:864:
+ const unsigned cores_needed = active_cores;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#994: FILE: examples/eventdev_pipeline/main.c:885:
+ const unsigned ndevs = rte_event_dev_count();
total: 0 errors, 22 warnings, 1024 lines checked
parent reply other threads:[~2017-04-21 9:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1492768299-84016-2-git-send-email-harry.van.haaren@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=20170421095402.63DD82C72@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=harry.van.haaren@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).