From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw62690[v3, 13/19] net/mlx5: add flow tag support
Date: 10 Nov 2019 13:35:24 -0800 [thread overview]
Message-ID: <ee68f5$8hn7oj@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/62690
_apply issues_
Submitter: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Date: 2019-11-07 17:09:58
Reply_mail: 1573146604-17803-14-git-send-email-viacheslavo@mellanox.com
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: ba465d0cf8672032e0339cda7ef3a083b2d8a2af
Repo:dpdk, CommitID: 6bbc5a9236250b708c6d1931e966c74da381b4f2
*Repo: dpdk-next-net-mlx
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
error: while searching for:
return rte_flow_error_set(error, EINVAL,
RTE_FLOW_ERROR_TYPE_ACTION, NULL,
"too many items to modify");
actions[i].action_type = MLX5_MODIFICATION_TYPE_SET;
actions[i].field = reg_to_field[conf->id];
actions[i].data0 = rte_cpu_to_be_32(actions[i].data0);
actions[i].data1 = conf->data;
++i;
resource->actions_num = i;
if (!resource->actions_num)
error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:872
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
*Repo: dpdk
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
error: while searching for:
return rte_flow_error_set(error, EINVAL,
RTE_FLOW_ERROR_TYPE_ACTION, NULL,
"too many items to modify");
actions[i].action_type = MLX5_MODIFICATION_TYPE_SET;
actions[i].field = reg_to_field[conf->id];
actions[i].data0 = rte_cpu_to_be_32(actions[i].data0);
actions[i].data1 = conf->data;
++i;
resource->actions_num = i;
if (!resource->actions_num)
error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:872
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
DPDK STV team
reply other threads:[~2019-11-10 21:35 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$8hn7oj@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).