From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: [dpdk-test-report] |FAILURE| pw37152 [PATCH v3 4/4] vfio: do not needlessly check for IOVA mode
Date: 16 Apr 2018 02:28:26 -0700 [thread overview]
Message-ID: <ca5293$1d25ij@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37152
_apply patch file failure_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed, 4 Apr 2018 15:40:44 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:419cb5e1e61f9ef3e2a84154f1f837c777512efa
Repo:dpdk-next-crypto, Branch:master, CommitID:9bbee42800166e09f8054cc1ca932b821ed149bf
Repo:dpdk-next-net, Branch:master, CommitID:acb6b4a192b73e9cc49aeb17bc6377afef66ae30
Repo:dpdk-next-virtio, Branch:master, CommitID:8adbe7e4847060d091c46abcbecd3dfea8362b7a
Repo:dpdk, Branch:master, CommitID:91f6191999cda8726ad7c3db1ff8731423236b46
Apply patch file failed:
Repo: dpdk
37152:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 FAILED at 681.
Hunk #2 FAILED at 784.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal_vfio.c.rej
Repo: dpdk-next-crypto
37152:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 FAILED at 681.
Hunk #2 FAILED at 784.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal_vfio.c.rej
Repo: dpdk-next-net
37152:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 FAILED at 681.
Hunk #2 FAILED at 784.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal_vfio.c.rej
Repo: dpdk-next-virtio
37152:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 FAILED at 681.
Hunk #2 FAILED at 784.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal_vfio.c.rej
Repo: dpdk-next-eventdev
37152:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 FAILED at 681.
Hunk #2 FAILED at 784.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal_vfio.c.rej
DPDK STV team
reply other threads:[~2018-04-16 9:28 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='ca5293$1d25ij@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=anatoly.burakov@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).