From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nikhil.rao@intel.com
Subject: [dpdk-test-report] |FAILURE| pw28649 [PATCH 3/4] eventdev: Add eventdev ethernet Rx adapter
Date: 13 Sep 2017 03:17:33 -0700 [thread overview]
Message-ID: <a2ed28$149ohdk@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2770 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/28649
_apply patch file failure_
Submitter: Nikhil Rao <nikhil.rao@intel.com>
Date: Thu, 14 Sep 2017 00:23:01 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
Repo:dpdk-next-crypto, Branch:master, CommitID:4d02833c0a45a7d777cc0a517c4452d30f314ad7
Repo:dpdk-next-net, Branch:master, CommitID:18b9b9d2320f1698a0bb4eeafdb2a6eabda24a3c
Repo:dpdk-next-virtio, Branch:master, CommitID:fee08fe0d67d46639d25c201738d9b1b867e443c
Repo:dpdk, Branch:master, CommitID:06791a4bcedf3eb97f05c13debff90272e3b0d54
Apply patch file failed:
Repo: dpdk
28649:
patching file lib/librte_eventdev/rte_event_eth_rx_adapter.h
patching file lib/librte_eventdev/rte_event_eth_rx_adapter.c
patching file lib/Makefile
patching file lib/librte_eventdev/Makefile
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #1 FAILED at 56.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eventdev/rte_eventdev_version.map.rej
Repo: dpdk-next-crypto
28649:
patching file lib/librte_eventdev/rte_event_eth_rx_adapter.h
patching file lib/librte_eventdev/rte_event_eth_rx_adapter.c
patching file lib/Makefile
patching file lib/librte_eventdev/Makefile
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #1 FAILED at 56.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eventdev/rte_eventdev_version.map.rej
Repo: dpdk-next-net
28649:
patching file lib/librte_eventdev/rte_event_eth_rx_adapter.h
patching file lib/librte_eventdev/rte_event_eth_rx_adapter.c
patching file lib/Makefile
patching file lib/librte_eventdev/Makefile
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #1 FAILED at 56.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eventdev/rte_eventdev_version.map.rej
Repo: dpdk-next-virtio
28649:
patching file lib/librte_eventdev/rte_event_eth_rx_adapter.h
patching file lib/librte_eventdev/rte_event_eth_rx_adapter.c
patching file lib/Makefile
patching file lib/librte_eventdev/Makefile
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #1 FAILED at 56.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eventdev/rte_eventdev_version.map.rej
Repo: dpdk-next-eventdev
28649:
patching file lib/librte_eventdev/rte_event_eth_rx_adapter.h
patching file lib/librte_eventdev/rte_event_eth_rx_adapter.c
patching file lib/Makefile
patching file lib/librte_eventdev/Makefile
patching file lib/librte_eventdev/rte_eventdev_version.map
Hunk #1 FAILED at 56.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eventdev/rte_eventdev_version.map.rej
DPDK STV team
reply other threads:[~2017-09-13 10:17 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='a2ed28$149ohdk@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=nikhil.rao@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).