From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-test-report] |WARNING| pw18811 [PATCH v2] Scheduler: add driver for scheduler crypto pmd
Date: Tue, 3 Jan 2017 18:07:54 +0100 (CET) [thread overview]
Message-ID: <20170103170754.CFBF75598@dpdk.org> (raw)
In-Reply-To: <1483463280-102879-1-git-send-email-roy.fan.zhang@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/18811
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1004: FILE: drivers/crypto/scheduler/rte_cryptodev_scheduler.h:170:
+ unsigned nb_options;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1007: FILE: drivers/crypto/scheduler/rte_cryptodev_scheduler.h:173:
+ unsigned nb_ioctls;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1440: FILE: drivers/crypto/scheduler/scheduler_pmd_ops.c:49:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1567: FILE: drivers/crypto/scheduler/scheduler_pmd_ops.c:176:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1597: FILE: drivers/crypto/scheduler/scheduler_pmd_ops.c:206:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1650: FILE: drivers/crypto/scheduler/scheduler_pmd_ops.c:259:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1673: FILE: drivers/crypto/scheduler/scheduler_pmd_ops.c:282:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1690: FILE: drivers/crypto/scheduler/scheduler_pmd_ops.c:299:
+ unsigned max_nb_sessions = sched_ctx->nb_slaves ? UINT32_MAX : 0;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1691: FILE: drivers/crypto/scheduler/scheduler_pmd_ops.c:300:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1807: FILE: drivers/crypto/scheduler/scheduler_pmd_ops.c:416:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1974: FILE: drivers/crypto/scheduler/scheduler_pmd_private.h:82:
+ unsigned nb_capabilities;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1976: FILE: drivers/crypto/scheduler/scheduler_pmd_private.h:84:
+ unsigned max_nb_queue_pairs;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#1979: FILE: drivers/crypto/scheduler/scheduler_pmd_private.h:87:
+ unsigned nb_slaves;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#2064: FILE: drivers/crypto/scheduler/scheduler_roundrobin.c:44:
+ unsigned nb_slaves;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#2066: FILE: drivers/crypto/scheduler/scheduler_roundrobin.c:46:
+ unsigned last_enq_slave_idx;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#2067: FILE: drivers/crypto/scheduler/scheduler_roundrobin.c:47:
+ unsigned last_deq_slave_idx;
total: 0 errors, 16 warnings, 2299 lines checked
parent reply other threads:[~2017-01-03 17:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1483463280-102879-1-git-send-email-roy.fan.zhang@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=20170103170754.CFBF75598@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=roy.fan.zhang@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).