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| pw58895 [PATCH v2 1/6] lib/ring: apis to support configurable element size
Date: Fri,  6 Sep 2019 21:06:51 +0200 (CEST)	[thread overview]
Message-ID: <20190906190651.B945C1F49E@dpdk.org> (raw)
In-Reply-To: <20190906190510.11146-2-honnappa.nagarahalli@arm.com>

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

_coding style issues_


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

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

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

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

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

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

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#169: FILE: lib/librte_ring/rte_ring.h:146:
+ssize_t rte_ring_get_memsize_elem(unsigned count, size_t esize);

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

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#224: FILE: lib/librte_ring/rte_ring.h:247:
+				size_t esize, int socket_id, unsigned flags);

total: 0 errors, 9 warnings, 184 lines checked

           reply	other threads:[~2019-09-06 19:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20190906190510.11146-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=20190906190651.B945C1F49E@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).