From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrzej Ostruszka <aostruszka@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw64669 [RFC PATCH 2/3] if_proxy: add preliminary Linux implementation
Date: Tue, 14 Jan 2020 15:26:21 +0100 (CET) [thread overview]
Message-ID: <20200114142621.0B7EC1C1BC@dpdk.org> (raw)
In-Reply-To: <20200114142517.29522-3-aostruszka@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/64669
_coding style issues_
WARNING:MISSING_BREAK: Possible switch case/default not preceded by break or fallthrough comment
#174: FILE: lib/librte_eal/linux/eal/eal_interrupts.c:902:
+ case RTE_INTR_HANDLE_NETLINK:
ERROR:CODE_INDENT: code indent should use tabs where possible
#515: FILE: lib/librte_if_proxy/rte_if_proxy.c:287:
+ uint16_t *ports, unsigned int num)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#515: FILE: lib/librte_if_proxy/rte_if_proxy.c:287:
+ uint16_t *ports, unsigned int num)$
ERROR:CODE_INDENT: code indent should use tabs where possible
#619: FILE: lib/librte_if_proxy/rte_if_proxy.c:391:
+^I^I RTA_DATA(attrs[IFLA_ADDRESS]);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#622: FILE: lib/librte_if_proxy/rte_if_proxy.c:394:
+^I^I RTE_ETHER_ADDR_LEN);$
ERROR:SPACING: space prohibited after that open parenthesis '('
#830: FILE: lib/librte_if_proxy/rte_if_proxy.c:602:
+ if ( !node->cbs.cfg_finished)
total: 4 errors, 2 warnings, 905 lines checked
parent reply other threads:[~2020-01-14 14:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200114142517.29522-3-aostruszka@marvell.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=20200114142621.0B7EC1C1BC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=aostruszka@marvell.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).