From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw66019doc: fix naming of Mellanox devices
Date: 26 Feb 2020 10:48:30 -0800 [thread overview]
Message-ID: <ee68f5$9epm6r@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3176 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/66019
_apply issues_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: 2020-02-24 19:52:14
Reply_mail: 20200224195214.3560827-1-thomas@monjalon.net
DPDK git baseline:
Repo:dpdk-next-net, CommitID: d7142fbae16f185e11bfa44be061399afc40a1be
Repo:dpdk, CommitID: d7142fbae16f185e11bfa44be061399afc40a1be
*Repo: dpdk-next-net
# Compile vdpa-oriented Mellanox ConnectX-6 & Bluefield (MLX5) PMD
#
CONFIG_RTE_LIBRTE_MLX5_VDPA_PMD=n
error: patch failed: config/common_base:361
error: config/common_base: patch does not apply
Checking patch drivers/net/mlx5/mlx5.c...
error: while searching for:
* key is specified in devargs
* - if DevX is enabled the inline mode is queried from the
--
* - otherwise L2 mode (18 bytes) is assumed for ConnectX-4/4LX
* and none (0 bytes) for other NICs
*
* @param spawn
error: patch failed: drivers/net/mlx5/mlx5.c:1724
error: drivers/net/mlx5/mlx5.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_rxtx.c...
error: while searching for:
/*
--
* This mode is supported by ConnectX-4LX only and imposes
* offload limitations, not supported:
* - ACL/Flows (metadata are becoming meaningless)
* - WQE Inline headers
error: patch failed: drivers/net/mlx5/mlx5_rxtx.c:5213
error: drivers/net/mlx5/mlx5_rxtx.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_txq.c...
error: while searching for:
* If there is requested minimal amount of data to inline
* we MUST enable inlining. This is a case for ConnectX-4
--
* and ConnectX-4LX which requires L2-L4 inlined to
* support E-Switch Flows.
*/
if (inlen_mode) {
error: patch failed: drivers/net/mlx5/mlx5_txq.c:983
error: drivers/net/mlx5/mlx5_txq.c: patch does not apply
*Repo: dpdk
# Compile vdpa-oriented Mellanox ConnectX-6 & Bluefield (MLX5) PMD
#
CONFIG_RTE_LIBRTE_MLX5_VDPA_PMD=n
error: patch failed: config/common_base:361
error: config/common_base: patch does not apply
Checking patch drivers/net/mlx5/mlx5.c...
error: while searching for:
* key is specified in devargs
* - if DevX is enabled the inline mode is queried from the
--
* - otherwise L2 mode (18 bytes) is assumed for ConnectX-4/4LX
* and none (0 bytes) for other NICs
*
* @param spawn
error: patch failed: drivers/net/mlx5/mlx5.c:1724
error: drivers/net/mlx5/mlx5.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_rxtx.c...
error: while searching for:
/*
--
* This mode is supported by ConnectX-4LX only and imposes
* offload limitations, not supported:
* - ACL/Flows (metadata are becoming meaningless)
* - WQE Inline headers
error: patch failed: drivers/net/mlx5/mlx5_rxtx.c:5213
error: drivers/net/mlx5/mlx5_rxtx.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_txq.c...
error: while searching for:
* If there is requested minimal amount of data to inline
* we MUST enable inlining. This is a case for ConnectX-4
--
* and ConnectX-4LX which requires L2-L4 inlined to
* support E-Switch Flows.
*/
if (inlen_mode) {
error: patch failed: drivers/net/mlx5/mlx5_txq.c:983
error: drivers/net/mlx5/mlx5_txq.c: patch does not apply
DPDK STV team
reply other threads:[~2020-02-26 18:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='ee68f5$9epm6r@orsmga001.jf.intel.com' \
--to=sys_stv@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).