From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw65320[v4, 12/25] common/mlx5: glue UAR allocation
Date: 17 Feb 2020 09:06:23 -0800 [thread overview]
Message-ID: <ee68f5$9c7non@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65320
_apply issues_
Submitter: Matan Azrad <matan@mellanox.com>
Date: 2020-01-29 12:38:37
Reply_mail: 1580301530-6643-13-git-send-email-matan@mellanox.com
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: 914397d6c1141235b48ca60249221976e9e08feb
Repo:dpdk, CommitID: 914397d6c1141235b48ca60249221976e9e08feb
*Repo: dpdk-next-net-mlx
.devx_subscribe_devx_event = mlx5_glue_devx_subscribe_devx_event,
.devx_subscribe_devx_event_fd = mlx5_glue_devx_subscribe_devx_event_fd,
.devx_get_event = mlx5_glue_devx_get_event,
};
error: patch failed: drivers/common/mlx5/mlx5_glue.c:1242
error: drivers/common/mlx5/mlx5_glue.c: patch does not apply
Checking patch drivers/common/mlx5/mlx5_glue.h...
error: while searching for:
#ifndef HAVE_IBV_DEVX_OBJ
struct mlx5dv_devx_obj;
struct mlx5dv_devx_umem { uint32_t umem_id; };
#endif
#ifndef HAVE_IBV_DEVX_ASYNC
error: patch failed: drivers/common/mlx5/mlx5_glue.h:66
error: drivers/common/mlx5/mlx5_glue.h: patch does not apply
*Repo: dpdk
.devx_subscribe_devx_event = mlx5_glue_devx_subscribe_devx_event,
.devx_subscribe_devx_event_fd = mlx5_glue_devx_subscribe_devx_event_fd,
.devx_get_event = mlx5_glue_devx_get_event,
};
error: patch failed: drivers/common/mlx5/mlx5_glue.c:1242
error: drivers/common/mlx5/mlx5_glue.c: patch does not apply
Checking patch drivers/common/mlx5/mlx5_glue.h...
error: while searching for:
#ifndef HAVE_IBV_DEVX_OBJ
struct mlx5dv_devx_obj;
struct mlx5dv_devx_umem { uint32_t umem_id; };
#endif
#ifndef HAVE_IBV_DEVX_ASYNC
error: patch failed: drivers/common/mlx5/mlx5_glue.h:66
error: drivers/common/mlx5/mlx5_glue.h: patch does not apply
DPDK STV team
reply other threads:[~2020-02-17 17:06 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='ee68f5$9c7non@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).