From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: borisp@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw28807 [PATCH 2/2] ethdev: update documentation for security action
Date: 20 Sep 2017 07:06:20 -0700 [thread overview]
Message-ID: <8a7c36$12vo1du@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/28807
_apply patch file failure_
Submitter: Boris Pismenny <borisp@mellanox.com>
Date: Sun, 17 Sep 2017 15:06:31 +0300
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:430b815c50d458c7207ce11d36aabf0184c86f79
Repo:dpdk-next-crypto, Branch:master, CommitID:176c6bcf3250fce8b054618df942acbf4add6d80
Repo:dpdk-next-net, Branch:master, CommitID:773427964063bb76bf52cb1f51b0f9d730b14310
Repo:dpdk-next-virtio, Branch:master, CommitID:fee08fe0d67d46639d25c201738d9b1b867e443c
Repo:dpdk, Branch:master, CommitID:3d2e0448ebb5c76fda6e988558793c070c3baded
Apply patch file failed:
Repo: dpdk
28807:
patching file lib/librte_ether/rte_flow.h
Hunk #1 FAILED at 1043.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ether/rte_flow.h.rej
Repo: dpdk-next-crypto
28807:
patching file lib/librte_ether/rte_flow.h
Hunk #1 FAILED at 1043.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ether/rte_flow.h.rej
Repo: dpdk-next-net
28807:
patching file lib/librte_ether/rte_flow.h
Hunk #1 FAILED at 1043.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ether/rte_flow.h.rej
Repo: dpdk-next-virtio
28807:
patching file lib/librte_ether/rte_flow.h
Hunk #1 FAILED at 1043.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ether/rte_flow.h.rej
Repo: dpdk-next-eventdev
28807:
patching file lib/librte_ether/rte_flow.h
Hunk #1 FAILED at 1043.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_ether/rte_flow.h.rej
DPDK STV team
reply other threads:[~2017-09-20 14:06 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='8a7c36$12vo1du@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=borisp@mellanox.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).