From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw60131[v5, 8/9] net/ice: add FDIR vxlan tunnel support
Date: 29 Sep 2019 21:31:48 -0700 [thread overview]
Message-ID: <ee68f5$85qa66@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/60131
_apply issues_
Submitter: Yahui Cao <yahui.cao@intel.com>
Date: 2019-09-30 11:45:46
Reply_mail: 20190930114547.74803-9-yahui.cao@intel.com
DPDK git baseline:
Repo:dpdk-next-net-intel, CommitID: 7403c1e35bb3d4dd110d03b3bb004b760981ef92
Repo:dpdk, CommitID: bd253daa7717835f88bbc58b09a94d0060380396
*Repo: dpdk-next-net-intel
struct rte_flow;
TAILQ_HEAD(ice_flow_list, rte_flow);
error: patch failed: drivers/net/ice/ice_ethdev.h:241
error: drivers/net/ice/ice_ethdev.h: patch does not apply
Checking patch drivers/net/ice/ice_fdir_filter.c...
error: drivers/net/ice/ice_fdir_filter.c: No such file or directory
*Repo: dpdk
struct rte_flow;
TAILQ_HEAD(ice_flow_list, rte_flow);
error: patch failed: drivers/net/ice/ice_ethdev.h:241
error: drivers/net/ice/ice_ethdev.h: patch does not apply
Checking patch drivers/net/ice/ice_fdir_filter.c...
error: drivers/net/ice/ice_fdir_filter.c: No such file or directory
DPDK STV team
reply other threads:[~2019-09-30 4:31 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$85qa66@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).