From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Moti Haimovsky <motih@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw53770 [PATCH v2] net/mlx5: remove TCF support from PMD
Date: Tue, 28 May 2019 15:13:45 +0200 (CEST) [thread overview]
Message-ID: <20190528131345.67B4F1B9BF@dpdk.org> (raw)
In-Reply-To: <de68e92186bee74478e31ef0ea65117769e8033e.1559044888.git.motih@mellanox.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/53770
_coding style issues_
ERROR:DOS_LINE_ENDINGS: DOS line endings
#48: FILE: doc/build-sdk-meson.txt:210:
+PMDs/libraries, for example -lmlx5 for librte-pmd-mlx5, or the static link^M$
ERROR:DOS_LINE_ENDINGS: DOS line endings
#463: FILE: drivers/net/mlx5/meson.build:16:
+libnames = [ 'mlx5', 'ibverbs' ]^M$
ERROR:DOS_LINE_ENDINGS: DOS line endings
#705: FILE: drivers/net/mlx5/mlx5_flow.c:1038:
+^Iif (attributes->transfer && !priv->config.dv_esw_en)^M$
ERROR:TRAILING_WHITESPACE: trailing whitespace
#714: FILE: drivers/net/mlx5/mlx5_flow.c:1295:
+ * mlx5 flow-specific (DV, verbs, etc.) supported header fields mask.^M$
ERROR:DOS_LINE_ENDINGS: DOS line endings
#725: FILE: drivers/net/mlx5/mlx5_flow.c:1785:
+^Iif (attr->transfer && priv->config.dv_esw_en)^M$
ERROR:DOS_LINE_ENDINGS: DOS line endings
#726: FILE: drivers/net/mlx5/mlx5_flow.c:1786:
+^I^Itype = MLX5_FLOW_TYPE_DV;^M$
ERROR:DOS_LINE_ENDINGS: DOS line endings
#727: FILE: drivers/net/mlx5/mlx5_flow.c:1787:
+^Iif (!attr->transfer)^M$
ERROR:TRAILING_WHITESPACE: trailing whitespace
#736: FILE: drivers/net/mlx5/mlx5_flow.c:1834:
+ * This function initializes device flow structure such as dv or verbs in^M$
ERROR:DOS_LINE_ENDINGS: DOS line endings
#7192: FILE: mk/rte.app.mk:178:
+_LDLIBS-$(CONFIG_RTE_LIBRTE_MLX5_PMD) += -lrte_pmd_mlx5^M$
total: 9 errors, 0 warnings, 701 lines checked
parent reply other threads:[~2019-05-28 13:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <de68e92186bee74478e31ef0ea65117769e8033e.1559044888.git.motih@mellanox.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=20190528131345.67B4F1B9BF@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=motih@mellanox.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).