From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jerin.jacob@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw24148 [PATCH] vfio: fix device unplug when several devices per vfio group Re: [PATCH] [PATCH] vfio: fix device unplug when several> devices per vfio group> > 28/04/2017 15:25 Burakov Anatoly:> >
Date: 08 May 2017 08:58:03 -0700 [thread overview]
Message-ID: <ffb989$2g6r2d@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/24148
_apply patch file failure_
Submitter: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Date: Mon, 8 May 2017 20:50:07 +0530Sun, 30 Apr 2017 19:29:49 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:70a969503bfcc2e8b0dd9fa71dae310c5358c9bc
Repo:dpdk-next-net, Branch:master, CommitID:59ba1c5ae7cea61ae7d310414209d0e9172474d9
Repo:dpdk-next-virtio, Branch:master, CommitID:ad06857e40c3d30f92ede00e840bbd8e6a69b703
Repo:dpdk, Branch:master, CommitID:59ba1c5ae7cea61ae7d310414209d0e9172474d9
Apply patch file failed:
Repo: dpdk
24148:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 FAILED at 100.
Repo: dpdk-next-crypto
24148:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 FAILED at 100.
Repo: dpdk-next-net
24148:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 FAILED at 100.
Repo: dpdk-next-virtio
24148:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 FAILED at 100.
Repo: dpdk-next-eventdev
24148:
patching file lib/librte_eal/linuxapp/eal/eal_vfio.c
Hunk #1 FAILED at 100.
DPDK STV team
reply other threads:[~2017-05-08 15:58 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='ffb989$2g6r2d@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=jerin.jacob@caviumnetworks.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).