From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: bernard.iremonger@intel.com
Subject: [dpdk-test-report] |FAILURE| pw22754 [PATCH v4 4/5] net/i40e: update destroy tunnel filter function
Date: 30 Mar 2017 02:17:58 -0700 [thread overview]
Message-ID: <e624e2$115vugi@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/22754
_apply patch file failure_
Submitter: Bernard Iremonger <bernard.iremonger@intel.com>
Date: Wed, 29 Mar 2017 17:41:48 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:78e5f2a8a133e885d5d0b5e49547b1cbcf3797fa
Repo:dpdk-next-crypto, Branch:master, CommitID:922b510880414efdadbce0061e2d4199a8626550
Repo:dpdk-next-net, Branch:master, CommitID:d1f78e9696cd39a5faed498ad7e8368c724945e4
Repo:dpdk-next-virtio, Branch:master, CommitID:8ec4aa31199c361151610ef54427d5f91c3dac8c
Repo:dpdk, Branch:master, CommitID:a6619414e0a93176d36b471ba3e5c1d552b65dd7
Apply patch file failed:
Repo: dpdk
22754:
patching file drivers/net/i40e/i40e_flow.c
Hunk #1 FAILED at 2170.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_flow.c.rej
Repo: dpdk-next-crypto
22754:
patching file drivers/net/i40e/i40e_flow.c
Hunk #1 FAILED at 2170.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_flow.c.rej
Repo: dpdk-next-net
22754:
patching file drivers/net/i40e/i40e_flow.c
Hunk #1 FAILED at 2170.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_flow.c.rej
Repo: dpdk-next-virtio
22754:
patching file drivers/net/i40e/i40e_flow.c
Hunk #1 FAILED at 2170.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_flow.c.rej
Repo: dpdk-next-eventdev
22754:
patching file drivers/net/i40e/i40e_flow.c
Hunk #1 FAILED at 2170.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/i40e/i40e_flow.c.rej
DPDK STV team
reply other threads:[~2017-03-30 9:18 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='e624e2$115vugi@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=bernard.iremonger@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).