automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Subject: [dpdk-test-report] |WARNING| pw60731 [PATCH v4 1/2] lib/ring: apis to support configurable element size
Date: Wed,  9 Oct 2019 04:47:54 +0200 (CEST)	[thread overview]
Message-ID: <20191009024754.C6D8A1C1D4@dpdk.org> (raw)
In-Reply-To: <20191009024709.38144-2-honnappa.nagarahalli@arm.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/60731

_coding style issues_


WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#88: FILE: lib/librte_ring/rte_ring.c:50:
+rte_ring_get_memsize_elem(unsigned count, unsigned esize)

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#88: FILE: lib/librte_ring/rte_ring.c:50:
+rte_ring_get_memsize_elem(unsigned count, unsigned esize)

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#122: FILE: lib/librte_ring/rte_ring.c:81:
+rte_ring_get_memsize(unsigned count)

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#139: FILE: lib/librte_ring/rte_ring.c:139:
+rte_ring_create_elem(const char *name, unsigned count, unsigned esize,

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#139: FILE: lib/librte_ring/rte_ring.c:139:
+rte_ring_create_elem(const char *name, unsigned count, unsigned esize,

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#140: FILE: lib/librte_ring/rte_ring.c:140:
+		int socket_id, unsigned flags)

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#159: FILE: lib/librte_ring/rte_ring.c:207:
+rte_ring_create(const char *name, unsigned count, int socket_id,

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#160: FILE: lib/librte_ring/rte_ring.c:208:
+		unsigned flags)

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#246: FILE: lib/librte_ring/rte_ring_elem.h:60:
+ssize_t rte_ring_get_memsize_elem(unsigned count, unsigned esize);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#246: FILE: lib/librte_ring/rte_ring_elem.h:60:
+ssize_t rte_ring_get_memsize_elem(unsigned count, unsigned esize);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#294: FILE: lib/librte_ring/rte_ring_elem.h:108:
+struct rte_ring *rte_ring_create_elem(const char *name, unsigned count,

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#295: FILE: lib/librte_ring/rte_ring_elem.h:109:
+				unsigned esize, int socket_id, unsigned flags);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#295: FILE: lib/librte_ring/rte_ring_elem.h:109:
+				unsigned esize, int socket_id, unsigned flags);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#317: FILE: lib/librte_ring/rte_ring_elem.h:131:
+		for (i = 0; i < (n & ((~(unsigned)0x7))); i += 8, idx += 8) { \

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#358: FILE: lib/librte_ring/rte_ring_elem.h:172:
+		for (i = 0; i < (n & ((~(unsigned)0x3))); i += 4, idx += 4) { \

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#423: FILE: lib/librte_ring/rte_ring_elem.h:237:
+		for (i = 0; i < (n & (~(unsigned)0x7)); i += 8, idx += 8) {\

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#464: FILE: lib/librte_ring/rte_ring_elem.h:278:
+		for (i = 0; i < (n & (~(unsigned)0x3)); i += 4, idx += 4) {\

total: 0 errors, 17 warnings, 1071 lines checked

           reply	other threads:[~2019-10-09  2:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20191009024709.38144-2-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=20191009024754.C6D8A1C1D4@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).