From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: thomas@monjalon.net
Subject: [dpdk-test-report] |FAILURE| pw38151 [PATCH v5 2/5] vhost: support selective datapath
Date: 26 Apr 2018 13:18:58 -0700 [thread overview]
Message-ID: <0590c7$1gnptf@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38151
_apply patch file failure_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Sun, 15 Apr 2018 19:39:10 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:eb8a86e275ef15a5455948d679d1a2c43dd4c740
Repo:dpdk-next-net, Branch:master, CommitID:e657a5d5fae02bcd8e62d4e57338d7d363e638c1
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:09f4aa2b955f9f9e2e662ca7c5f3fa7258ef4614
Apply patch file failed:
Repo: dpdk
38151:
patching file lib/librte_vhost/meson.build
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/meson.build.rej
Repo: dpdk-next-crypto
38151:
patching file lib/librte_vhost/meson.build
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/meson.build.rej
Repo: dpdk-next-net
38151:
patching file lib/librte_vhost/meson.build
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/meson.build.rej
Repo: dpdk-next-virtio
38151:
patching file lib/librte_vhost/meson.build
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/meson.build.rej
Repo: dpdk-next-eventdev
38151:
patching file lib/librte_vhost/meson.build
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/meson.build.rej
DPDK STV team
reply other threads:[~2018-04-26 20:19 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='0590c7$1gnptf@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).