From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jingjing Wu <jingjing.wu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw30627 [PATCH RFC 4/9] net/avf: enable basic Rx Tx func
Date: Fri, 20 Oct 2017 10:36:41 +0200 (CEST) [thread overview]
Message-ID: <20171020083641.0851C1B1F1@dpdk.org> (raw)
In-Reply-To: <1508488012-82704-5-git-send-email-jingjing.wu@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/30627
_coding style issues_
CHECK:BRACES: Unbalanced braces around else statement
#386: FILE: drivers/net/avf/avf_rxtx.c:926:
+ } else
WARNING:DEEP_INDENTATION: Too many leading tabs - consider code refactoring
#657: FILE: drivers/net/avf/avf_rxtx.c:1197:
+ if (nb_tx == 0)
CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#701: FILE: drivers/net/avf/avf_rxtx.c:1241:
+ "type_cmd_tso_mss: %#"PRIx64";
",
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#701: FILE: drivers/net/avf/avf_rxtx.c:1241:
+ "type_cmd_tso_mss: %#"PRIx64";
",
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#724: FILE: drivers/net/avf/avf_rxtx.c:1264:
+ "buf_dma_addr: %#"PRIx64";
"
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#771: FILE: drivers/net/avf/avf_rxtx.c:1311:
+ (unsigned)txq->port_id, (unsigned)txq->queue_id,
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#771: FILE: drivers/net/avf/avf_rxtx.c:1311:
+ (unsigned)txq->port_id, (unsigned)txq->queue_id,
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#772: FILE: drivers/net/avf/avf_rxtx.c:1312:
+ (unsigned)tx_id, (unsigned)nb_tx);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#772: FILE: drivers/net/avf/avf_rxtx.c:1312:
+ (unsigned)tx_id, (unsigned)nb_tx);
total: 0 errors, 5 warnings, 4 checks, 867 lines checked
parent reply other threads:[~2017-10-20 8:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1508488012-82704-5-git-send-email-jingjing.wu@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=20171020083641.0851C1B1F1@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jingjing.wu@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).