From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Phil Yang <phil.yang@arm.com>
Subject: [dpdk-test-report] |WARNING| pw44916 [v2, 2/3] kni: fix kni fifo synchronization
Date: Wed, 19 Sep 2018 15:44:59 +0200 (CEST) [thread overview]
Message-ID: <20180919134459.DAF424C9F@dpdk.org> (raw)
In-Reply-To: <1537364560-4124-2-git-send-email-phil.yang@arm.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/44916
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#47: FILE: lib/librte_eal/linuxapp/eal/include/exec-env/rte_kni_common.h:61:
+ unsigned write; /**< Next position to be written*/
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#48: FILE: lib/librte_eal/linuxapp/eal/include/exec-env/rte_kni_common.h:62:
+ unsigned read; /**< Next position to be read */
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#64: FILE: lib/librte_kni/rte_kni_fifo.h:33:
+ unsigned fifo_read = __atomic_load_n(&fifo->read,
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#67: FILE: lib/librte_kni/rte_kni_fifo.h:36:
+ unsigned fifo_read = fifo->read;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#90: FILE: lib/librte_kni/rte_kni_fifo.h:65:
+ unsigned fifo_write = __atomic_load_n(&fifo->write, __ATOMIC_ACQUIRE);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#116: FILE: lib/librte_kni/rte_kni_fifo.h:93:
+ unsigned fifo_write = __atomic_load_n(&fifo->write,
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#118: FILE: lib/librte_kni/rte_kni_fifo.h:95:
+ unsigned fifo_read = __atomic_load_n(&fifo->read,
total: 0 errors, 7 warnings, 76 lines checked
parent reply other threads:[~2018-09-19 13:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1537364560-4124-2-git-send-email-phil.yang@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=20180919134459.DAF424C9F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=phil.yang@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).