From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw62426[04/20] net/mlx5: refactor flow structure
Date: 05 Nov 2019 03:23:28 -0800 [thread overview]
Message-ID: <ee68f5$8g1thn@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/62426
_apply issues_
Submitter: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Date: 2019-11-05 08:01:39
Reply_mail: 1572940915-29416-5-git-send-email-viacheslavo@mellanox.com
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: e71ae0791749b393902694f23ece4420cd5fdde7
Repo:dpdk, CommitID: 38383890b21f995c3dafa177298d744e1db0be84
Apply patchset failed, the failed patch is: http://dpdk.org/patch/62420
*Repo: dpdk
flow->queue = (void *)(flow + 1);
LIST_INIT(&flow->dev_flows);
if (rss && rss->types) {
unsigned int graph_root;
error: patch failed: drivers/net/mlx5/mlx5_flow.c:2815
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow.h...
Hunk #1 succeeded at 363 (offset -54 lines).
Hunk #2 succeeded at 381 (offset -54 lines).
Hunk #3 succeeded at 407 (offset -54 lines).
--
/**< Bit-fields of detected actions, see MLX5_FLOW_ACTION_*. */
union {
#ifdef HAVE_IBV_FLOW_DV_SUPPORT
struct mlx5_flow_dv dv;
error: patch failed: drivers/net/mlx5/mlx5_flow.h:473
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
Hunk #1 succeeded at 1434 (offset -149 lines).
Hunk #2 succeeded at 2595 (offset -149 lines).
Hunk #3 succeeded at 3903 (offset -162 lines).
--
if (flow->transfer) {
dv->actions[n++] = priv->sh->esw_drop_action;
} else {
dv->hrxq = mlx5_hrxq_drop_new(dev);
error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:6242
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_verbs.c...
Hunk #4 succeeded at 1489 (offset 1 line).
Hunk #5 succeeded at 1501 (offset 1 line).
Hunk #6 succeeded at 1513 (offset 1 line).
DPDK STV team
reply other threads:[~2019-11-05 11:23 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$8g1thn@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).