From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kuba Kozak <kubax.kozak@intel.com>
Subject: [dpdk-test-report] |WARNING| pw21129 [PATCH 2/4] net/e1000: add grouping of xstats for e1000 driver
Date: Thu, 2 Mar 2017 15:29:38 +0100 (CET) [thread overview]
Message-ID: <20170302142938.CA48F6CB4@dpdk.org> (raw)
In-Reply-To: <1488470875-26716-3-git-send-email-kubax.kozak@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/21129
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#71: FILE: drivers/net/e1000/igb_ethdev.c:121:
+ unsigned n, uint64_t group_mask);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#78: FILE: drivers/net/e1000/igb_ethdev.c:128:
+ __rte_unused unsigned limit,
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#301: FILE: drivers/net/e1000/igb_ethdev.c:1919:
+ __rte_unused unsigned limit,
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#305: FILE: drivers/net/e1000/igb_ethdev.c:1922:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#306: FILE: drivers/net/e1000/igb_ethdev.c:1923:
+ unsigned count = 0;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#333: FILE: drivers/net/e1000/igb_ethdev.c:1950:
+ unsigned n)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#347: FILE: drivers/net/e1000/igb_ethdev.c:1982:
+ unsigned n, uint64_t group_mask)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#353: FILE: drivers/net/e1000/igb_ethdev.c:1988:
+ unsigned i;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#354: FILE: drivers/net/e1000/igb_ethdev.c:1989:
+ unsigned count = 0;
total: 0 errors, 9 warnings, 0 checks, 331 lines checked
parent reply other threads:[~2017-03-02 14:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1488470875-26716-3-git-send-email-kubax.kozak@intel.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=20170302142938.CA48F6CB4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=kubax.kozak@intel.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).