From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xiao.w.wang@intel.com
Subject: [dpdk-test-report] |FAILURE| pw32793 [PATCH RFC 2/4] vhost: expose vhost lib to app
Date: 11 Jan 2018 18:17:03 -0800 [thread overview]
Message-ID: <1f4ae4$p90td@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/32793
_apply patch file failure_
Submitter: Xiao Wang <xiao.w.wang@intel.com>
Date: Fri, 29 Dec 2017 10:05:02 -0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18280212534a7dcb61021393afd7394eaa1ff51e
Repo:dpdk-next-crypto, Branch:master, CommitID:052f7e585e9c7c5f2bbacb230812df95e774e98e
Repo:dpdk-next-net, Branch:master, CommitID:92c214d207cab768574e6fb668a1eab1793fdafe
Repo:dpdk-next-virtio, Branch:master, CommitID:814339ba7eea13d132508af2cccec2f73568e2d0
Repo:dpdk, Branch:master, CommitID:6c7001480ac6356ff0a4995f3ed495ed9c866061
Apply patch file failed:
Repo: dpdk
32793:
patching file lib/librte_vhost/Makefile
Hunk #1 FAILED at 52.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/Makefile.rej
Repo: dpdk-next-crypto
32793:
patching file lib/librte_vhost/Makefile
Hunk #1 FAILED at 52.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/Makefile.rej
Repo: dpdk-next-net
32793:
patching file lib/librte_vhost/Makefile
Hunk #1 FAILED at 52.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/Makefile.rej
Repo: dpdk-next-virtio
32793:
patching file lib/librte_vhost/Makefile
Hunk #1 FAILED at 52.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/Makefile.rej
Repo: dpdk-next-eventdev
32793:
patching file lib/librte_vhost/Makefile
Hunk #1 FAILED at 52.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/Makefile.rej
DPDK STV team
reply other threads:[~2018-01-12 2: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='1f4ae4$p90td@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=xiao.w.wang@intel.com \
/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).