automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Sergey Vyazmitinov <s.vyazmitinov@brain4net.com>
Subject: [dpdk-test-report] |WARNING| pw19096 [PATCH] kni: use bulk functions to allocate and free mbufs
Date: Wed, 11 Jan 2017 04:24:46 +0100 (CET)	[thread overview]
Message-ID: <20170111032446.B136569FC@dpdk.org> (raw)
In-Reply-To: <1483048216-2936-1-git-send-email-s.vyazmitinov@brain4net.com>

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

_coding style issues_


WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#80: FILE: lib/librte_kni/rte_kni.c:593:
+	unsigned freeing;

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#99: FILE: lib/librte_kni/rte_kni.c:605:
+	unsigned count, allocated, put;

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#126: FILE: lib/librte_kni/rte_kni.c:635:
+	for (unsigned i = 0; i < allocated; i++)

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#139: FILE: lib/librte_kni/rte_kni.c:643:
+		for (unsigned j = put; j < allocated; j++) {

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#193: FILE: lib/librte_mbuf/rte_mbuf.h:1277:
+		struct rte_mbuf **mbufs, unsigned n)

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#196: FILE: lib/librte_mbuf/rte_mbuf.h:1280:
+	unsigned i;

total: 0 errors, 6 warnings, 140 lines checked

           reply	other threads:[~2017-01-11  3:24 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1483048216-2936-1-git-send-email-s.vyazmitinov@brain4net.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=20170111032446.B136569FC@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=s.vyazmitinov@brain4net.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).