From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw62565[17/19] net/mlx5: split meter flow
Date: 08 Nov 2019 19:04:24 -0800 [thread overview]
Message-ID: <ee68f5$8hcaga@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/62565
_apply issues_
Submitter: Suanming Mou <suanmingm@mellanox.com>
Date: 2019-11-06 15:11:26
Reply_mail: 1573053090-179521-18-git-send-email-suanmingm@mellanox.com
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: d31c160fb7e309bd5c84cf156056496217da1674
Repo:dpdk, CommitID: 20d3f48be1d1d1d84da2881e72769aed430b3c44
*Repo: dpdk-next-net-mlx
ret = flow_create_split_metadata(dev, flow, attr, items,
actions, external, error);
assert(ret <= 0);
return ret;
error: patch failed: drivers/net/mlx5/mlx5_flow.c:3723
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow.h...
error: while searching for:
struct mlx5_flow_verbs verbs;
};
uint32_t qrss_id; /**< Uniqie Q/RSS suffix subflow tag. */
bool external; /**< true if the flow is created external to PMD. */
};
error: patch failed: drivers/net/mlx5/mlx5_flow.h:521
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
*Repo: dpdk
static int
flow_null_validate(struct rte_eth_dev *dev __rte_unused,
const struct rte_flow_attr *attr __rte_unused,
error: patch failed: drivers/net/mlx5/mlx5_flow.c:2309
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow.h...
error: while searching for:
struct mlx5_flow_verbs verbs;
};
uint32_t qrss_id; /**< Uniqie Q/RSS suffix subflow tag. */
bool external; /**< true if the flow is created external to PMD. */
};
error: patch failed: drivers/net/mlx5/mlx5_flow.h:521
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
DPDK STV team
reply other threads:[~2019-11-09 3:04 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$8hcaga@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).