From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw56742net/mlx5: fix NVGRE matching
Date: 18 Jul 2019 14:53:17 -0700 [thread overview]
Message-ID: <ee68f5$7g8p69@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/56742
_apply issues_
Submitter: Dekel Peled <dekelp@mellanox.com>
Date: 2019-07-18 19:42:35
Reply_mail: 3cd91c82dfa7f0feb325c0ed866659c07230c9fb.1563478228.git.dekelp@mellanox.com
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: dd442062f4114193b148e91b3c5860b16c3b7f54
Repo:dpdk, CommitID: b58b3c96752eb9b11b41ad5077f288dd4003f072
*Repo: dpdk-next-net-mlx
#define MLX5_FLOW_LAYER_IPV6_ENCAP (1u << 22)
/* Outer Masks. */
#define MLX5_FLOW_LAYER_OUTER_L3 \
error: patch failed: drivers/net/mlx5/mlx5_flow.h:58
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
Hunk #1 succeeded at 2968 (offset 2 lines).
Hunk #2 succeeded at 2975 (offset 2 lines).
Hunk #3 succeeded at 3928 (offset 2 lines).
*Repo: dpdk
#define MLX5_FLOW_LAYER_IPV6_ENCAP (1u << 22)
/* Outer Masks. */
#define MLX5_FLOW_LAYER_OUTER_L3 \
error: patch failed: drivers/net/mlx5/mlx5_flow.h:58
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
Hunk #1 succeeded at 2398 (offset -568 lines).
error: while searching for:
gre_item = items;
--
break;
case RTE_FLOW_ITEM_TYPE_GRE_KEY:
ret = mlx5_flow_validate_item_gre_key
(items, item_flags, gre_item, error);
error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:2974
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_rxtx.h...
Hunk #1 succeeded at 39 (offset -1 lines).
DPDK STV team
reply other threads:[~2019-07-18 21:53 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$7g8p69@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).