From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Keith Wiles <keith.wiles@intel.com>
Subject: [dpdk-test-report] |WARNING| pw19839 [PATCH] net/tap: fix IFF_MULTI_QUEUE in older kernels not found
Date: Fri, 20 Jan 2017 15:25:36 +0100 (CET) [thread overview]
Message-ID: <20170120142536.24E4F37B2@dpdk.org> (raw)
In-Reply-To: <20170120142519.23455-1-keith.wiles@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/19839
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#63: FILE: drivers/net/tap/rte_eth_tap.c:156:
+ if (RTE_PMD_TAP_MAX_QUEUES > 1) {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#64: FILE: drivers/net/tap/rte_eth_tap.c:157:
+ RTE_LOG(DEBUG, PMD, "TUN/TAP device only one queue
");$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#64: FILE: drivers/net/tap/rte_eth_tap.c:157:
+ RTE_LOG(DEBUG, PMD, "TUN/TAP device only one queue
");$
ERROR:CODE_INDENT: code indent should use tabs where possible
#65: FILE: drivers/net/tap/rte_eth_tap.c:158:
+ goto error;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#65: FILE: drivers/net/tap/rte_eth_tap.c:158:
+ goto error;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#66: FILE: drivers/net/tap/rte_eth_tap.c:159:
+ } else {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#67: FILE: drivers/net/tap/rte_eth_tap.c:160:
+ ifr.ifr_flags |= IFF_ONE_QUEUE;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#67: FILE: drivers/net/tap/rte_eth_tap.c:160:
+ ifr.ifr_flags |= IFF_ONE_QUEUE;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#68: FILE: drivers/net/tap/rte_eth_tap.c:161:
+ RTE_LOG(DEBUG, PMD, "Single queue only support
");$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#68: FILE: drivers/net/tap/rte_eth_tap.c:161:
+ RTE_LOG(DEBUG, PMD, "Single queue only support
");$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#69: FILE: drivers/net/tap/rte_eth_tap.c:162:
+ }$
total: 4 errors, 7 warnings, 0 checks, 22 lines checked
parent reply other threads:[~2017-01-20 14:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170120142519.23455-1-keith.wiles@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=20170120142536.24E4F37B2@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=keith.wiles@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).