From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: junjie.j.chen@intel.com
Subject: [dpdk-test-report] |FAILURE| pw37972 [PATCH v6 1/2] vhost: add support for interrupt mode
Date: 25 Apr 2018 03:04:45 -0700 [thread overview]
Message-ID: <a7de25$16gcsd@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2769 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37972
_apply patch file failure_
Submitter: junjie.j.chen@intel.com
Date: Thu, 12 Apr 2018 12:28:34 -0400
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:e90cf125c8aa735f0c4f8e0ef5f669ac9f104f82
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:2ed9bf330709e75c2f066f6ec13ece1ecdb4e9db
Apply patch file failed:
Repo: dpdk
37972:
patching file drivers/net/vhost/rte_eth_vhost.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
7 out of 7 hunks ignored -- saving rejects to file drivers/net/vhost/rte_eth_vhost.c.rej
patching file lib/librte_vhost/vhost.c
Hunk #1 FAILED at 545.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/vhost.c.rej
Repo: dpdk-next-crypto
37972:
patching file drivers/net/vhost/rte_eth_vhost.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
7 out of 7 hunks ignored -- saving rejects to file drivers/net/vhost/rte_eth_vhost.c.rej
patching file lib/librte_vhost/vhost.c
Hunk #1 FAILED at 545.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/vhost.c.rej
Repo: dpdk-next-net
37972:
patching file drivers/net/vhost/rte_eth_vhost.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
7 out of 7 hunks ignored -- saving rejects to file drivers/net/vhost/rte_eth_vhost.c.rej
patching file lib/librte_vhost/vhost.c
Hunk #1 FAILED at 545.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/vhost.c.rej
Repo: dpdk-next-virtio
37972:
patching file drivers/net/vhost/rte_eth_vhost.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
7 out of 7 hunks ignored -- saving rejects to file drivers/net/vhost/rte_eth_vhost.c.rej
patching file lib/librte_vhost/vhost.c
Hunk #1 FAILED at 545.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_vhost/vhost.c.rej
Repo: dpdk-next-eventdev
37972:
patching file drivers/net/vhost/rte_eth_vhost.c
Hunk #2 succeeded at 714 (offset -1 lines).
Hunk #3 succeeded at 730 (offset -1 lines).
Hunk #4 FAILED at 740.
Hunk #6 FAILED at 924.
Hunk #7 succeeded at 1163 (offset 1 line).
2 out of 7 hunks FAILED -- saving rejects to file drivers/net/vhost/rte_eth_vhost.c.rej
patching file lib/librte_vhost/vhost.c
DPDK STV team
reply other threads:[~2018-04-25 10:04 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='a7de25$16gcsd@fmsmga002.fm.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).