From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(71740) [v1, 4/4] vdpa/mlx5: support queue update
Date: 18 Jun 2020 12:28:13 -0700 [thread overview]
Message-ID: <fecc85$ag5nad@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/71740
_apply issues_
Submitter: Matan Azrad <matan@mellanox.com>
Date: 2020-06-18 16:28:06
Reply_mail: 1592497686-433697-5-git-send-email-matan@mellanox.com
DPDK git baseline:
Repo:dpdk-next-virtio, CommitID: 454bcd44902f85a8c498d7d8420a30199756506c
Repo:dpdk, CommitID: f3687f251e14689900e24b39bf187bf251208407
* Repo: dpdk-next-virtio
{
int did = rte_vhost_get_vdpa_device_id(vid);
error: patch failed: drivers/vdpa/mlx5/mlx5_vdpa.c:142
error: drivers/vdpa/mlx5/mlx5_vdpa.c: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa.h...
Hunk #1 succeeded at 69 (offset -1 lines).
--
pthread_t timer_tid;
pthread_mutex_t timer_lock;
error: patch failed: drivers/vdpa/mlx5/mlx5_vdpa.h:103
error: drivers/vdpa/mlx5/mlx5_vdpa.h: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa_virtq.c...
* Repo: dpdk
{
int did = rte_vhost_get_vdpa_device_id(vid);
error: patch failed: drivers/vdpa/mlx5/mlx5_vdpa.c:142
error: drivers/vdpa/mlx5/mlx5_vdpa.c: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa.h...
error: while searching for:
--
struct mlx5_devx_obj *virtq;
struct mlx5_devx_obj *counters;
error: patch failed: drivers/vdpa/mlx5/mlx5_vdpa.h:70
error: drivers/vdpa/mlx5/mlx5_vdpa.h: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa_virtq.c...
error: while searching for:
--
}
error: patch failed: drivers/vdpa/mlx5/mlx5_vdpa_virtq.c:79
error: drivers/vdpa/mlx5/mlx5_vdpa_virtq.c: patch does not apply
DPDK STV team
reply other threads:[~2020-06-18 19: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='fecc85$ag5nad@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).