From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrzej Ostruszka <aostruszka@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw64668 [RFC PATCH 1/3] lib: introduce IF proxy library (API)
Date: Tue, 14 Jan 2020 15:26:18 +0100 (CET) [thread overview]
Message-ID: <20200114142618.B84571C1B1@dpdk.org> (raw)
In-Reply-To: <20200114142517.29522-2-aostruszka@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/64668
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#165: FILE: lib/librte_if_proxy/rte_if_proxy.h:70:
+ RTE_IFPX_DEFAULT,^I/**< Use default proxy type for given arch. */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#166: FILE: lib/librte_if_proxy/rte_if_proxy.h:71:
+ RTE_IFPX_TAP,^I/**< Use Tap based port for proxy. */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#167: FILE: lib/librte_if_proxy/rte_if_proxy.h:72:
+ RTE_IFPX_KNI^I/**< Use KNI based port for proxy. */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#288: FILE: lib/librte_if_proxy/rte_if_proxy.h:193:
+ RTE_IFPX_MAC_CHANGE = 1ULL << 0, /**< @see mac_change callback */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#289: FILE: lib/librte_if_proxy/rte_if_proxy.h:194:
+ RTE_IFPX_MTU_CHANGE = 1ULL << 1, /**< @see mtu_change callback */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#290: FILE: lib/librte_if_proxy/rte_if_proxy.h:195:
+ RTE_IFPX_LINK_CHANGE = 1ULL << 2, /**< @see link_change callback */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#291: FILE: lib/librte_if_proxy/rte_if_proxy.h:196:
+ RTE_IFPX_ADDR_ADD = 1ULL << 3, /**< @see addr_add callback */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#292: FILE: lib/librte_if_proxy/rte_if_proxy.h:197:
+ RTE_IFPX_ADDR_DEL = 1ULL << 4, /**< @see addr_del callback */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#293: FILE: lib/librte_if_proxy/rte_if_proxy.h:198:
+ RTE_IFPX_ADDR6_ADD = 1ULL << 5, /**< @see addr6_add callback */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#294: FILE: lib/librte_if_proxy/rte_if_proxy.h:199:
+ RTE_IFPX_ADDR6_DEL = 1ULL << 6, /**< @see addr6_del callback */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#295: FILE: lib/librte_if_proxy/rte_if_proxy.h:200:
+ RTE_IFPX_ROUTE_ADD = 1ULL << 7, /**< @see route_add callback */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#296: FILE: lib/librte_if_proxy/rte_if_proxy.h:201:
+ RTE_IFPX_ROUTE_DEL = 1ULL << 8, /**< @see route_del callback */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#297: FILE: lib/librte_if_proxy/rte_if_proxy.h:202:
+ RTE_IFPX_ROUTE6_ADD = 1ULL << 9, /**< @see route6_add callback */$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#298: FILE: lib/librte_if_proxy/rte_if_proxy.h:203:
+ RTE_IFPX_ROUTE6_DEL = 1ULL << 10, /**< @see route6_del callback */$
total: 0 errors, 14 warnings, 364 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-2-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=20200114142618.B84571C1B1@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).