From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jakub Grajciar <jgrajcia@cisco.com>
Subject: [dpdk-test-report] |WARNING| pw54904 [PATCH v2] net/memif: multi-process support
Date: Wed, 19 Jun 2019 16:31:30 +0200 (CEST) [thread overview]
Message-ID: <20190619143130.47E331C30E@dpdk.org> (raw)
In-Reply-To: <20190618084851.5322-1-jgrajcia@cisco.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/54904
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#321: FILE: drivers/net/memif/rte_eth_memif.c:146:
+ free(reply);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#321: FILE: drivers/net/memif/rte_eth_memif.c:146:
+ free(reply);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#322: FILE: drivers/net/memif/rte_eth_memif.c:147:
+ return -ENOMEM;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#322: FILE: drivers/net/memif/rte_eth_memif.c:147:
+ return -ENOMEM;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#327: FILE: drivers/net/memif/rte_eth_memif.c:152:
+ free(reply);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#327: FILE: drivers/net/memif/rte_eth_memif.c:152:
+ free(reply);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#328: FILE: drivers/net/memif/rte_eth_memif.c:153:
+ return -1;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#328: FILE: drivers/net/memif/rte_eth_memif.c:153:
+ return -1;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#338: FILE: drivers/net/memif/rte_eth_memif.c:163:
+ free(reply);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#338: FILE: drivers/net/memif/rte_eth_memif.c:163:
+ free(reply);$
CHECK:BRACES: Blank lines aren't necessary before a close brace '}'
#341: FILE: drivers/net/memif/rte_eth_memif.c:166:
+
+}
WARNING:BRACES: braces {} are not necessary for single statement blocks
#831: FILE: drivers/net/memif/rte_eth_memif.c:805:
+ for (i = 0; i < dev->data->nb_rx_queues; i++) {
+ (*dev->dev_ops->rx_queue_release)(dev->data->rx_queues[i]);
+ }
WARNING:BRACES: braces {} are not necessary for single statement blocks
#834: FILE: drivers/net/memif/rte_eth_memif.c:808:
+ for (i = 0; i < dev->data->nb_tx_queues; i++) {
+ (*dev->dev_ops->tx_queue_release)(dev->data->tx_queues[i]);
+ }
WARNING:UNNECESSARY_ELSE: else is not generally useful after a break or return
#987: FILE: drivers/net/memif/rte_eth_memif.c:1303:
+ return 0;
+ } else {
total: 5 errors, 8 warnings, 1 checks, 933 lines checked
parent reply other threads:[~2019-06-19 14:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190618084851.5322-1-jgrajcia@cisco.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=20190619143130.47E331C30E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jgrajcia@cisco.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).