From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: shacharbe@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw31555 [PATCH v1 2/2] net/mlx4: load libmlx4 and libibverbs in run-time
Date: 23 Nov 2017 09:00:54 -0800 [thread overview]
Message-ID: <b81db2$akj4d@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4991 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/31555
_apply patch file failure_
Submitter: Shachar Beiser <shacharbe@mellanox.com>
Date: Thu, 23 Nov 2017 12:18:23 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:d84aad650401a122cb75bd5811e49b03ef3dc49d
Repo:dpdk-next-crypto, Branch:master, CommitID:d84aad650401a122cb75bd5811e49b03ef3dc49d
Repo:dpdk-next-net, Branch:master, CommitID:d84aad650401a122cb75bd5811e49b03ef3dc49d
Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
Repo:dpdk, Branch:master, CommitID:d84aad650401a122cb75bd5811e49b03ef3dc49d
Apply patch file failed:
Repo: dpdk
31555:
patching file config/common_base
patching file drivers/net/mlx4/Makefile
patching file drivers/net/mlx4/lib/mlx4_dll.c
patching file drivers/net/mlx4/lib/mlx4_dll.h
patching file drivers/net/mlx4/mlx4.c
patching file drivers/net/mlx4/mlx4.h
patching file drivers/net/mlx4/mlx4_ethdev.c
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_mr.c
patching file drivers/net/mlx4/mlx4_prm.h
patching file drivers/net/mlx4/mlx4_rxq.c
patching file drivers/net/mlx4/mlx4_rxtx.c
patching file drivers/net/mlx4/mlx4_rxtx.h
patching file drivers/net/mlx4/mlx4_txq.c
patching file mk/rte.app.mk
Hunk #1 FAILED at 54.
Hunk #2 FAILED at 143.
2 out of 2 hunks FAILED -- saving rejects to file mk/rte.app.mk.rej
Repo: dpdk-next-crypto
31555:
patching file config/common_base
patching file drivers/net/mlx4/Makefile
patching file drivers/net/mlx4/lib/mlx4_dll.c
patching file drivers/net/mlx4/lib/mlx4_dll.h
patching file drivers/net/mlx4/mlx4.c
patching file drivers/net/mlx4/mlx4.h
patching file drivers/net/mlx4/mlx4_ethdev.c
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_mr.c
patching file drivers/net/mlx4/mlx4_prm.h
patching file drivers/net/mlx4/mlx4_rxq.c
patching file drivers/net/mlx4/mlx4_rxtx.c
patching file drivers/net/mlx4/mlx4_rxtx.h
patching file drivers/net/mlx4/mlx4_txq.c
patching file mk/rte.app.mk
Hunk #1 FAILED at 54.
Hunk #2 FAILED at 143.
2 out of 2 hunks FAILED -- saving rejects to file mk/rte.app.mk.rej
Repo: dpdk-next-net
31555:
patching file config/common_base
patching file drivers/net/mlx4/Makefile
patching file drivers/net/mlx4/lib/mlx4_dll.c
patching file drivers/net/mlx4/lib/mlx4_dll.h
patching file drivers/net/mlx4/mlx4.c
patching file drivers/net/mlx4/mlx4.h
patching file drivers/net/mlx4/mlx4_ethdev.c
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_mr.c
patching file drivers/net/mlx4/mlx4_prm.h
patching file drivers/net/mlx4/mlx4_rxq.c
patching file drivers/net/mlx4/mlx4_rxtx.c
patching file drivers/net/mlx4/mlx4_rxtx.h
patching file drivers/net/mlx4/mlx4_txq.c
patching file mk/rte.app.mk
Hunk #1 FAILED at 54.
Hunk #2 FAILED at 143.
2 out of 2 hunks FAILED -- saving rejects to file mk/rte.app.mk.rej
Repo: dpdk-next-virtio
31555:
patching file config/common_base
Hunk #1 succeeded at 214 (offset -15 lines).
patching file drivers/net/mlx4/Makefile
Hunk #2 succeeded at 56 with fuzz 1.
Hunk #3 succeeded at 86 (offset -1 lines).
patching file drivers/net/mlx4/lib/mlx4_dll.c
patching file drivers/net/mlx4/lib/mlx4_dll.h
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 49.
Hunk #2 succeeded at 718 (offset 5 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
patching file drivers/net/mlx4/mlx4_ethdev.c
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_mr.c
Hunk #1 succeeded at 45 (offset -2 lines).
patching file drivers/net/mlx4/mlx4_prm.h
patching file drivers/net/mlx4/mlx4_rxq.c
Hunk #1 FAILED at 46.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4_rxq.c.rej
patching file drivers/net/mlx4/mlx4_rxtx.c
Hunk #1 succeeded at 45 (offset 1 line).
patching file drivers/net/mlx4/mlx4_rxtx.h
patching file drivers/net/mlx4/mlx4_txq.c
patching file mk/rte.app.mk
Hunk #1 FAILED at 54.
Hunk #2 FAILED at 143.
2 out of 2 hunks FAILED -- saving rejects to file mk/rte.app.mk.rej
Repo: dpdk-next-eventdev
31555:
patching file config/common_base
patching file drivers/net/mlx4/Makefile
patching file drivers/net/mlx4/lib/mlx4_dll.c
patching file drivers/net/mlx4/lib/mlx4_dll.h
patching file drivers/net/mlx4/mlx4.c
patching file drivers/net/mlx4/mlx4.h
patching file drivers/net/mlx4/mlx4_ethdev.c
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_mr.c
patching file drivers/net/mlx4/mlx4_prm.h
patching file drivers/net/mlx4/mlx4_rxq.c
patching file drivers/net/mlx4/mlx4_rxtx.c
patching file drivers/net/mlx4/mlx4_rxtx.h
patching file drivers/net/mlx4/mlx4_txq.c
patching file mk/rte.app.mk
Hunk #1 FAILED at 54.
Hunk #2 FAILED at 143.
2 out of 2 hunks FAILED -- saving rejects to file mk/rte.app.mk.rej
DPDK STV team
reply other threads:[~2017-11-23 17:00 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='b81db2$akj4d@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=shacharbe@mellanox.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).