From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: tiwei.bie@intel.com
Subject: [dpdk-test-report] |FAILURE| pw27034 [PATCH RFC 2/6] vhost: optimize enqueue path
Date: 18 Jul 2017 19:12:31 -0700 [thread overview]
Message-ID: <e624e2$12bfhbk@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/27034
_apply patch file failure_
Submitter: Tiwei Bie <tiwei.bie@intel.com>
Date: Tue, 18 Jul 2017 23:40:21 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:76ee670f6a91f27eed7e06d2272db68f527c2a8b
Repo:dpdk-next-crypto, Branch:master, CommitID:79776eff44fbb0713d0850dd422a80cd27a170fe
Repo:dpdk-next-net, Branch:master, CommitID:97bd47c9bbd431dba78cc607fb25416fc23a3b69
Repo:dpdk-next-virtio, Branch:master, CommitID:23079506d3566585c9b3bde703ddf5db81d50186
Repo:dpdk, Branch:master, CommitID:7146aa19aca1ae78a04f620fbedb64190c219409
Apply patch file failed:
Repo: dpdk
27034:
patching file lib/librte_vhost/virtio_net.c
Hunk #1 FAILED at 583.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/virtio_net.c.rej
Repo: dpdk-next-crypto
27034:
patching file lib/librte_vhost/virtio_net.c
Hunk #1 FAILED at 583.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/virtio_net.c.rej
Repo: dpdk-next-net
27034:
patching file lib/librte_vhost/virtio_net.c
Hunk #1 FAILED at 583.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/virtio_net.c.rej
Repo: dpdk-next-virtio
27034:
patching file lib/librte_vhost/virtio_net.c
Hunk #1 FAILED at 583.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/virtio_net.c.rej
Repo: dpdk-next-eventdev
27034:
patching file lib/librte_vhost/virtio_net.c
Hunk #1 FAILED at 583.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/virtio_net.c.rej
DPDK STV team
reply other threads:[~2017-07-19 2:12 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='e624e2$12bfhbk@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=tiwei.bie@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).