From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(72237) [v3, 06/14] vhost: replace vDPA device ID in Vhost
Date: 28 Jun 2020 09:01:46 -0700 [thread overview]
Message-ID: <fecc85$aiovep@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/72237
_apply issues_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: 2020-06-26 13:27:04
Reply_mail: 20200626132712.1437673-7-maxime.coquelin@redhat.com
DPDK git baseline:
Repo:dpdk-next-virtio, CommitID: 4a756a8c2f9dbf1f43e2638028931331e2a617eb
Repo:dpdk, CommitID: 6248368a9ae1eadf6b7fb05ab37497afdb714429
Apply patchset failed, the failed patch is: http://dpdk.org/patch/72234
* Repo: dpdk
if (list == NULL) {
DRV_LOG(ERR, "Invalid vDPA device: %p", vdev);
error: patch failed: drivers/vdpa/ifc/ifcvf_vdpa.c:881
error: drivers/vdpa/ifc/ifcvf_vdpa.c: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa.c...
error: while searching for:
--
mlx5_vdpa_find_priv_resource_by_vdev(vdev);
error: patch failed: drivers/vdpa/mlx5/mlx5_vdpa.c:129
error: drivers/vdpa/mlx5/mlx5_vdpa.c: patch does not apply
Checking patch examples/vdpa/main.c...
Hunk #1 succeeded at 145 (offset -4 lines).
--
rte_vhost_driver_get_queue_num;
rte_vhost_get_log_base;
error: patch failed: lib/librte_vhost/rte_vhost_version.map:43
error: lib/librte_vhost/rte_vhost_version.map: patch does not apply
Checking patch lib/librte_vhost/socket.c...
Checking patch lib/librte_vhost/vhost.c...
DPDK STV team
next reply other threads:[~2020-06-28 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 16:01 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-26 18:40 sys_stv
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='fecc85$aiovep@orsmga001.jf.intel.com' \
--to=sys_stv@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).