From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: junjie.j.chen@intel.com
Subject: [dpdk-test-report] |FAILURE| pw37853 [PATCH] net/vhost: fix vhost invalid state
Date: 23 Apr 2018 18:08:28 -0700 [thread overview]
Message-ID: <0590c7$1ftd4l@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37853
_apply patch file failure_
Submitter: junjie.j.chen@intel.com
Date: Wed, 11 Apr 2018 02:54:31 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:fa1759db3581b68b66aa2d52ee2dffd8677c5b2c
Repo:dpdk-next-net, Branch:master, CommitID:2c3a970e6ee03be3f7157c4abb313193954f753b
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:9553e6e408883b3677e208dc66049bcd7f758529
Apply patch file failed:
Repo: dpdk
37853:
patching file drivers/net/vhost/rte_eth_vhost.c
Hunk #1 FAILED at 655.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/vhost/rte_eth_vhost.c.rej
Repo: dpdk-next-crypto
37853:
patching file drivers/net/vhost/rte_eth_vhost.c
Hunk #1 FAILED at 655.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/vhost/rte_eth_vhost.c.rej
Repo: dpdk-next-net
37853:
patching file drivers/net/vhost/rte_eth_vhost.c
Hunk #1 FAILED at 655.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/vhost/rte_eth_vhost.c.rej
Repo: dpdk-next-virtio
37853:
patching file drivers/net/vhost/rte_eth_vhost.c
Hunk #1 FAILED at 655.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/vhost/rte_eth_vhost.c.rej
Repo: dpdk-next-eventdev
37853:
patching file drivers/net/vhost/rte_eth_vhost.c
Hunk #1 FAILED at 655.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/vhost/rte_eth_vhost.c.rej
DPDK STV team
reply other threads:[~2018-04-24 1:08 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$1ftd4l@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=junjie.j.chen@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).