From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: [dpdk-test-report] |FAILURE| pw35743 [PATCH v2 24/41] vfio: allow to map other memory regions
Date: 07 Mar 2018 12:37:32 -0800 [thread overview]
Message-ID: <f7a79a$165tqi@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3545 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/35743
_apply patch file failure_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed, 7 Mar 2018 16:56:54 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:92924b207b124c156f7b6dff75110d6af83d971f
Repo:dpdk-next-crypto, Branch:master, CommitID:92924b207b124c156f7b6dff75110d6af83d971f
Repo:dpdk-next-net, Branch:master, CommitID:317debafe8e154cc81f5053c7424c8cc41ac8812
Repo:dpdk-next-virtio, Branch:master, CommitID:fc33e147ae5e63a28c2b2c9bec5ad378c612ca36
Repo:dpdk, Branch:master, CommitID:c06ddf9698e0c2a9653cfa971f9ddc205065662c
Apply patch file failed:
Repo: dpdk
35743:
patching file lib/librte_eal/bsdapp/eal/eal.c
Hunk #1 succeeded at 746 (offset -9 lines).
Hunk #2 succeeded at 783 (offset -9 lines).
patching file lib/librte_eal/common/include/rte_vfio.h
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #4 FAILED at 686.
Hunk #5 FAILED at 718.
Hunk #6 succeeded at 832 (offset -54 lines).
Hunk #7 succeeded at 907 (offset -54 lines).
2 out of 7 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal_vfio.c.rej
patching file lib/librte_eal/linuxapp/eal/eal_vfio.h
Repo: dpdk-next-crypto
35743:
patching file lib/librte_eal/bsdapp/eal/eal.c
Hunk #1 succeeded at 746 (offset -9 lines).
Hunk #2 succeeded at 783 (offset -9 lines).
patching file lib/librte_eal/common/include/rte_vfio.h
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #4 FAILED at 686.
Hunk #5 FAILED at 718.
Hunk #6 succeeded at 832 (offset -54 lines).
Hunk #7 succeeded at 907 (offset -54 lines).
2 out of 7 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal_vfio.c.rej
patching file lib/librte_eal/linuxapp/eal/eal_vfio.h
Repo: dpdk-next-net
35743:
patching file lib/librte_eal/bsdapp/eal/eal.c
Hunk #1 succeeded at 746 (offset -9 lines).
Hunk #2 succeeded at 783 (offset -9 lines).
patching file lib/librte_eal/common/include/rte_vfio.h
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #4 FAILED at 686.
Hunk #5 FAILED at 718.
Hunk #6 succeeded at 832 (offset -54 lines).
Hunk #7 succeeded at 907 (offset -54 lines).
2 out of 7 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal_vfio.c.rej
patching file lib/librte_eal/linuxapp/eal/eal_vfio.h
Repo: dpdk-next-virtio
35743:
patching file lib/librte_eal/bsdapp/eal/eal.c
Hunk #1 succeeded at 746 (offset -9 lines).
Hunk #2 succeeded at 783 (offset -9 lines).
patching file lib/librte_eal/common/include/rte_vfio.h
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #4 FAILED at 686.
Hunk #5 FAILED at 718.
Hunk #6 succeeded at 832 (offset -54 lines).
Hunk #7 succeeded at 907 (offset -54 lines).
2 out of 7 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal_vfio.c.rej
patching file lib/librte_eal/linuxapp/eal/eal_vfio.h
Repo: dpdk-next-eventdev
35743:
patching file lib/librte_eal/bsdapp/eal/eal.c
Hunk #1 succeeded at 746 (offset -9 lines).
Hunk #2 succeeded at 783 (offset -9 lines).
patching file lib/librte_eal/common/include/rte_vfio.h
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #4 FAILED at 686.
Hunk #5 FAILED at 718.
Hunk #6 succeeded at 832 (offset -54 lines).
Hunk #7 succeeded at 907 (offset -54 lines).
2 out of 7 hunks FAILED -- saving rejects to file lib/librte_eal/linuxapp/eal/eal_vfio.c.rej
patching file lib/librte_eal/linuxapp/eal/eal_vfio.h
DPDK STV team
reply other threads:[~2018-03-07 20:37 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='f7a79a$165tqi@orsmga002.jf.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).