From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw65937[v2, 2/2] net/mlx5: fix lack of match information in meter
Date: 24 Feb 2020 18:41:43 -0800 [thread overview]
Message-ID: <ee68f5$9e8865@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65937
_apply issues_
Submitter: Suanming Mou <suanmingm@mellanox.com>
Date: 2020-02-20 04:00:44
Reply_mail: 1582171244-84418-3-git-send-email-suanmingm@mellanox.com
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: fbd54248bb18040166a3e6d792282bd5ca5ed240
Repo:dpdk, CommitID: fbd54248bb18040166a3e6d792282bd5ca5ed240
*Repo: dpdk-next-net-mlx
struct rte_flow *flow,
const struct rte_flow_attr *attr,
const struct rte_flow_item items[],
const struct rte_flow_action actions[],
error: patch failed: drivers/net/mlx5/mlx5_flow.c:3794
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
error: while searching for:
* Pointer to item specification.
* @param[out] attr
--
switch (item->type) {
case RTE_FLOW_ITEM_TYPE_GRE:
case RTE_FLOW_ITEM_TYPE_NVGRE:
error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:85
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
*Repo: dpdk
struct rte_flow *flow,
const struct rte_flow_attr *attr,
const struct rte_flow_item items[],
const struct rte_flow_action actions[],
error: patch failed: drivers/net/mlx5/mlx5_flow.c:3794
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
error: while searching for:
* Pointer to item specification.
* @param[out] attr
--
switch (item->type) {
case RTE_FLOW_ITEM_TYPE_GRE:
case RTE_FLOW_ITEM_TYPE_NVGRE:
error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:85
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
DPDK STV team
reply other threads:[~2020-02-25 2:41 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$9e8865@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).