automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Joyce Kong <joyce.kong@arm.com>
Subject: [dpdk-test-report] |WARNING| pw97096 [PATCH] kni: remove non-C11 path from FIFO sync
Date: Thu, 19 Aug 2021 08:05:55 +0200 (CEST)	[thread overview]
Message-ID: <20210819060555.26E4E122434@dpdk.org> (raw)
In-Reply-To: <20210819060442.19014-1-joyce.kong@arm.com>

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

_coding style issues_


WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#75: FILE: lib/kni/rte_kni_common.h:61:
+	unsigned write;     /**< Next position to be written*/

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#76: FILE: lib/kni/rte_kni_common.h:62:
+	unsigned read;      /**< Next position to be read */

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#128: FILE: lib/kni/rte_kni_fifo.h:30:
+	unsigned fifo_read = __atomic_load_n(&fifo->read, __ATOMIC_ACQUIRE);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#146: FILE: lib/kni/rte_kni_fifo.h:52:
+	unsigned fifo_write = __atomic_load_n(&fifo->write, __ATOMIC_ACQUIRE);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#165: FILE: lib/kni/rte_kni_fifo.h:71:
+	unsigned fifo_write = __atomic_load_n(&fifo->write, __ATOMIC_ACQUIRE);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#166: FILE: lib/kni/rte_kni_fifo.h:72:
+	unsigned fifo_read = __atomic_load_n(&fifo->read, __ATOMIC_ACQUIRE);

total: 0 errors, 6 warnings, 104 lines checked

       reply	other threads:[~2021-08-19  6:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210819060442.19014-1-joyce.kong@arm.com>
2021-08-19  6:05 ` checkpatch [this message]
2021-08-19  6:39 ` [dpdk-test-report] |SUCCESS| pw97096 [dpdk-dev] " 0-day Robot

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=20210819060555.26E4E122434@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=joyce.kong@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).