From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Subject: [dpdk-test-report] |WARNING| pw58896 [PATCH v2 2/6] lib/ring: add template to support different element sizes
Date: Fri, 6 Sep 2019 21:06:53 +0200 (CEST) [thread overview]
Message-ID: <20190906190653.2F31B1BF59@dpdk.org> (raw)
In-Reply-To: <20190906190510.11146-3-honnappa.nagarahalli@arm.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/58896
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#103: FILE: lib/librte_ring/rte_ring_template.c:34:
+__RTE_RING_CONCAT(rte_ring_get_memsize)(unsigned count)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#110: FILE: lib/librte_ring/rte_ring_template.c:41:
+__RTE_RING_CONCAT(rte_ring_create)(const char *name, unsigned count,
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#111: FILE: lib/librte_ring/rte_ring_template.c:42:
+ int socket_id, unsigned flags)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#168: FILE: lib/librte_ring/rte_ring_template.h:47:
+ssize_t __RTE_RING_CONCAT(rte_ring_get_memsize)(unsigned count);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#173: FILE: lib/librte_ring/rte_ring_template.h:52:
+__RTE_RING_CONCAT(rte_ring_create)(const char *name, unsigned count,
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#174: FILE: lib/librte_ring/rte_ring_template.h:53:
+ int socket_id, unsigned flags);
total: 0 errors, 6 warnings, 395 lines checked
parent reply other threads:[~2019-09-06 19:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190906190510.11146-3-honnappa.nagarahalli@arm.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=20190906190653.2F31B1BF59@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=honnappa.nagarahalli@arm.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).