From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Allain Legacy <allain.legacy@windriver.com>
Subject: [dpdk-test-report] |WARNING| pw20741 [PATCH 07/16] net/avp: driver registration
Date: Sat, 25 Feb 2017 02:24:46 +0100 (CET) [thread overview]
Message-ID: <20170225012446.B6FDEF932@dpdk.org> (raw)
In-Reply-To: <1487985795-136044-8-git-send-email-allain.legacy@windriver.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/20741
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#253: FILE: drivers/net/avp/avp_ethdev.c:119:
+ unsigned guest_mbuf_size; /**< local pool mbuf size */
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#254: FILE: drivers/net/avp/avp_ethdev.c:120:
+ unsigned host_mbuf_size; /**< host mbuf size */
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#255: FILE: drivers/net/avp/avp_ethdev.c:121:
+ unsigned max_rx_pkt_len; /**< maximum receive unit */
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#258: FILE: drivers/net/avp/avp_ethdev.c:124:
+ unsigned num_tx_queues; /**< Negotiated number of transmit queues */
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#259: FILE: drivers/net/avp/avp_ethdev.c:125:
+ unsigned max_tx_queues; /**< Maximum number of transmit queues */
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#260: FILE: drivers/net/avp/avp_ethdev.c:126:
+ unsigned num_rx_queues; /**< Negotiated number of receive queues */
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#261: FILE: drivers/net/avp/avp_ethdev.c:127:
+ unsigned max_rx_queues; /**< Maximum number of receive queues */
total: 0 errors, 7 warnings, 282 lines checked
parent reply other threads:[~2017-02-25 1:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1487985795-136044-8-git-send-email-allain.legacy@windriver.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=20170225012446.B6FDEF932@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=allain.legacy@windriver.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).