From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw56099[v5, 1/4] ethdev: add GRE key field to flow API
Date: 19 Jul 2019 13:56:25 -0700 [thread overview]
Message-ID: <ee68f5$7gi956@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/56099
_apply issues_
Submitter: Xiaoyu Min <jackmin@mellanox.com>
Date: 2019-07-04 16:30:11
Reply_mail: ff2873b552a885f4bf95a2acf0524c8b9ae62c56.1562257159.git.jackmin@mellanox.com
DPDK git baseline:
Repo:dpdk-next-net, CommitID: 232581d91daf2956f3c2026b8aaeed1005a14dc9
Repo:dpdk, CommitID: c0ed103a027385f14f352d46ff5450826b2746b7
*Repo: dpdk-next-net
MK_FLOW_ITEM(META, sizeof(struct rte_flow_item_meta)),
};
/** Generate flow_action[] entry. */
error: patch failed: lib/librte_ethdev/rte_flow.c:74
error: lib/librte_ethdev/rte_flow.c: patch does not apply
Checking patch lib/librte_ethdev/rte_flow.h...
error: while searching for:
* See struct rte_flow_item_meta.
*/
RTE_FLOW_ITEM_TYPE_META,
};
/**
error: patch failed: lib/librte_ethdev/rte_flow.h:421
error: lib/librte_ethdev/rte_flow.h: patch does not apply
*Repo: dpdk
MK_FLOW_ITEM(META, sizeof(struct rte_flow_item_meta)),
};
/** Generate flow_action[] entry. */
error: patch failed: lib/librte_ethdev/rte_flow.c:74
error: lib/librte_ethdev/rte_flow.c: patch does not apply
Checking patch lib/librte_ethdev/rte_flow.h...
error: while searching for:
* See struct rte_flow_item_meta.
*/
RTE_FLOW_ITEM_TYPE_META,
};
/**
error: patch failed: lib/librte_ethdev/rte_flow.h:421
error: lib/librte_ethdev/rte_flow.h: patch does not apply
DPDK STV team
next reply other threads:[~2019-07-19 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 20:56 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-05 13:45 sys_stv
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$7gi956@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).