From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: [dpdk-test-report] |FAILURE| pw32447 [PATCH 22/23] vfio: allow to map other memory regions
Date: 07 Jan 2018 18:17:23 -0800 [thread overview]
Message-ID: <a797f1$iq9e7@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3224 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/32447
_apply patch file failure_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Tue, 19 Dec 2017 11:04:41 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:36d020c107ba65a584784a3f52484ea1698d4f9d
Repo:dpdk-next-crypto, Branch:master, CommitID:8b083ec68aef37d6dbc3751fe45acd35d344b469
Repo:dpdk-next-net, Branch:master, CommitID:929a80374047dacd785c42db8e240901af041e9a
Repo:dpdk-next-virtio, Branch:master, CommitID:75b3e3d09c9a52e0ed17a3a8253c5e9ffa90603a
Repo:dpdk, Branch:master, CommitID:a12f226789156ed1f2f5639567408379fe2e6a46
Apply patch file failed:
Repo: dpdk
32447:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 succeeded at 11 (offset -29 lines).
Hunk #2 succeeded at 23 (offset -29 lines).
Hunk #3 succeeded at 352 (offset -29 lines).
Hunk #4 succeeded at 373 (offset -29 lines).
Hunk #5 FAILED at 716.
Hunk #6 FAILED at 749.
Hunk #7 succeeded at 833 (offset -81 lines).
Hunk #8 succeeded at 895 (offset -81 lines).
2 out of 8 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
Hunk #1 succeeded at 19 (offset -29 lines).
Hunk #2 succeeded at 111 (offset -29 lines).
Hunk #3 succeeded at 121 (offset -29 lines).
Repo: dpdk-next-crypto
32447:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 succeeded at 11 (offset -29 lines).
Hunk #2 succeeded at 23 (offset -29 lines).
Hunk #3 succeeded at 352 (offset -29 lines).
Hunk #4 succeeded at 373 (offset -29 lines).
Hunk #5 FAILED at 716.
Hunk #6 FAILED at 749.
Hunk #7 succeeded at 833 (offset -81 lines).
Hunk #8 succeeded at 895 (offset -81 lines).
2 out of 8 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
Hunk #1 succeeded at 19 (offset -29 lines).
Hunk #2 succeeded at 111 (offset -29 lines).
Hunk #3 succeeded at 121 (offset -29 lines).
Repo: dpdk-next-net
32447:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #5 FAILED at 716.
Hunk #6 FAILED at 749.
Hunk #7 succeeded at 862 (offset -52 lines).
Hunk #8 succeeded at 924 (offset -52 lines).
2 out of 8 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
32447:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #5 FAILED at 716.
Hunk #6 FAILED at 749.
Hunk #7 succeeded at 862 (offset -52 lines).
Hunk #8 succeeded at 924 (offset -52 lines).
2 out of 8 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
32447:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #5 FAILED at 716.
Hunk #6 FAILED at 749.
Hunk #7 succeeded at 862 (offset -52 lines).
Hunk #8 succeeded at 924 (offset -52 lines).
2 out of 8 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-01-08 2:17 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='a797f1$iq9e7@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).