From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw52017[v3, 1/6] net/mlx: remove debug messages on datapath
Date: 01 Apr 2019 18:50:27 -0700 [thread overview]
Message-ID: <e75792$6hfnir@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3723 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/52017
_apply issues_
Submitter: Yongseok Koh <yskoh@mellanox.com>
Date: 2019-04-01 21:17:52
Reply_mail: 20190401211757.26241-2-yskoh@mellanox.com
DPDK git baseline:
Repo:dpdk-master, CommitID: a9d64ecc4cc3ce1a48f96b06f24430900c15e728
Repo:dpdk-next-eventdev, CommitID: 7a1ccc24874e251957513aba0520500f873e276a
Repo:dpdk-next-net, CommitID: 484217a17ee094df024bfa19557c0a15537e7a57
Repo:dpdk-next-crypto, CommitID: b9bc82a71ea1faae88e535511213754004099b98
Repo:dpdk-next-virtio, CommitID: daf8de5c41dfbe40f354ff009f5791db348e0b09
*Repo: dpdk-master
Checking patch drivers/net/mlx4/mlx4_mr.c...
error: while searching for:
struct mlx4_mr_ctrl *mr_ctrl = &rxq->mr_ctrl;
struct mlx4_priv *priv = rxq->priv;
DEBUG("Rx queue %u: miss on top-half, mru=%u, head=%u, addr=%p",
rxq->stats.idx, mr_ctrl->mru, mr_ctrl->head, (void *)addr);
return mlx4_mr_addr2mr_bh(ETH_DEV(priv), mr_ctrl, addr);
}
error: patch failed: drivers/net/mlx4/mlx4_mr.c:1039
error: drivers/net/mlx4/mlx4_mr.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_mr.c...
Hunk #1 succeeded at 1029 (offset -2 lines).
Hunk #2 succeeded at 1051 (offset -2 lines).
*Repo: dpdk-next-eventdev
Checking patch drivers/net/mlx4/mlx4_mr.c...
error: while searching for:
struct mlx4_mr_ctrl *mr_ctrl = &rxq->mr_ctrl;
struct mlx4_priv *priv = rxq->priv;
DEBUG("Rx queue %u: miss on top-half, mru=%u, head=%u, addr=%p",
rxq->stats.idx, mr_ctrl->mru, mr_ctrl->head, (void *)addr);
return mlx4_mr_addr2mr_bh(ETH_DEV(priv), mr_ctrl, addr);
}
error: patch failed: drivers/net/mlx4/mlx4_mr.c:1039
error: drivers/net/mlx4/mlx4_mr.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_mr.c...
Hunk #1 succeeded at 1029 (offset -2 lines).
Hunk #2 succeeded at 1051 (offset -2 lines).
*Repo: dpdk-next-net
Checking patch drivers/net/mlx4/mlx4_mr.c...
error: while searching for:
struct mlx4_mr_ctrl *mr_ctrl = &rxq->mr_ctrl;
struct mlx4_priv *priv = rxq->priv;
DEBUG("Rx queue %u: miss on top-half, mru=%u, head=%u, addr=%p",
rxq->stats.idx, mr_ctrl->mru, mr_ctrl->head, (void *)addr);
return mlx4_mr_addr2mr_bh(ETH_DEV(priv), mr_ctrl, addr);
}
error: patch failed: drivers/net/mlx4/mlx4_mr.c:1039
error: drivers/net/mlx4/mlx4_mr.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_mr.c...
Hunk #1 succeeded at 1029 (offset -2 lines).
Hunk #2 succeeded at 1051 (offset -2 lines).
*Repo: dpdk-next-crypto
Checking patch drivers/net/mlx4/mlx4_mr.c...
error: while searching for:
struct mlx4_mr_ctrl *mr_ctrl = &rxq->mr_ctrl;
struct mlx4_priv *priv = rxq->priv;
DEBUG("Rx queue %u: miss on top-half, mru=%u, head=%u, addr=%p",
rxq->stats.idx, mr_ctrl->mru, mr_ctrl->head, (void *)addr);
return mlx4_mr_addr2mr_bh(ETH_DEV(priv), mr_ctrl, addr);
}
error: patch failed: drivers/net/mlx4/mlx4_mr.c:1039
error: drivers/net/mlx4/mlx4_mr.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_mr.c...
Hunk #1 succeeded at 1029 (offset -2 lines).
Hunk #2 succeeded at 1051 (offset -2 lines).
*Repo: dpdk-next-virtio
Checking patch drivers/net/mlx4/mlx4_mr.c...
error: while searching for:
struct mlx4_mr_ctrl *mr_ctrl = &rxq->mr_ctrl;
struct mlx4_priv *priv = rxq->priv;
DEBUG("Rx queue %u: miss on top-half, mru=%u, head=%u, addr=%p",
rxq->stats.idx, mr_ctrl->mru, mr_ctrl->head, (void *)addr);
return mlx4_mr_addr2mr_bh(ETH_DEV(priv), mr_ctrl, addr);
}
error: patch failed: drivers/net/mlx4/mlx4_mr.c:1039
error: drivers/net/mlx4/mlx4_mr.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_mr.c...
Hunk #1 succeeded at 1028 (offset -3 lines).
Hunk #2 succeeded at 1050 (offset -3 lines).
DPDK STV team
reply other threads:[~2019-04-02 1:50 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='e75792$6hfnir@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).