From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
Subject: [dpdk-test-report] |WARNING| pw37077 [PATCH dpdk-dev v1 2/5] eventdev: add crypto adapter implementation
Date: Wed, 4 Apr 2018 08:56:31 +0200 (CEST) [thread overview]
Message-ID: <20180404065631.B01D41BBB3@dpdk.org> (raw)
In-Reply-To: <1522824999-61614-1-git-send-email-abhinandan.gujjar@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/37077
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#184: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:95:
+ unsigned len;
WARNING:MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided
#195: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:106:
+#define RTE_EVENT_CRYPTO_ADAPTER_ID_VALID_OR_ERR_RET(id, retval) do { \
+ if (!eca_valid_id(id)) { \
+ RTE_EDEV_LOG_ERR("Invalid crypto adapter id = %d
", id); \
+ return retval; \
+ } \
+} while (0)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#396: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:307:
+ struct rte_event *ev, unsigned cnt)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#402: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:313:
+ unsigned i, n = 0;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#403: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:314:
+ unsigned ret = 0;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#405: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:316:
+ unsigned len = 0;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#532: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:443:
+ unsigned max_enq)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#536: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:447:
+ unsigned nb_enq, nb_enqueued = 0;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#573: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:484:
+ unsigned retry;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#574: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:485:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#641: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:552:
+ unsigned queues = 0;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#704: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:615:
+ unsigned max_ops)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#707: FILE: lib/librte_eventdev/rte_event_crypto_adapter.c:618:
+ unsigned e_cnt, d_cnt;
total: 0 errors, 13 warnings, 1590 lines checked
parent reply other threads:[~2018-04-04 6:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1522824999-61614-1-git-send-email-abhinandan.gujjar@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=20180404065631.B01D41BBB3@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=abhinandan.gujjar@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).