From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: nickcooper-zhangtonghao <nic@opencloud.tech>
Subject: [dpdk-test-report] |WARNING| pw18903 [PATCH 2/5] vmxnet3: Avoid memory leak in vmxnet3_dev_rx_queue_setup.
Date: Thu, 5 Jan 2017 11:43:26 +0100 (CET) [thread overview]
Message-ID: <20170105104326.6F6BBF612@dpdk.org> (raw)
In-Reply-To: <1483612983-3545-2-git-send-email-nic@opencloud.tech>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/18903
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#74: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:939:
+ if (dev->data->rx_queues[queue_idx] != NULL) {$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (4, 12)
#74: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:939:
+ if (dev->data->rx_queues[queue_idx] != NULL) {
+ vmxnet3_dev_rx_queue_release(dev->data->rx_queues[queue_idx]);
ERROR:CODE_INDENT: code indent should use tabs where possible
#75: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:940:
+ vmxnet3_dev_rx_queue_release(dev->data->rx_queues[queue_idx]);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#75: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:940:
+ vmxnet3_dev_rx_queue_release(dev->data->rx_queues[queue_idx]);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#76: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:941:
+ dev->data->rx_queues[queue_idx] = NULL;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#76: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:941:
+ dev->data->rx_queues[queue_idx] = NULL;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#77: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:942:
+ }$
total: 2 errors, 5 warnings, 0 checks, 42 lines checked
parent reply other threads:[~2017-01-05 10:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1483612983-3545-2-git-send-email-nic@opencloud.tech>]
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=20170105104326.6F6BBF612@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nic@opencloud.tech \
--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).