From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Alexander Kozyrev <akozyrev@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw144997 [PATCH v2] drivers: fix error CQE handling
Date: Fri, 4 Oct 2024 03:58:39 +0800 [thread overview]
Message-ID: <202410031958.493Jwdsp3709327@localhost.localdomain> (raw)
In-Reply-To: <20241003202605.867419-1-akozyrev@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/144997
_apply patch failure_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Thu, 3 Oct 2024 23:26:05 +0300
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2b843cac232eb3f2fa79e4254e21766817e2019f
Apply patch set 144997 failed:
Checking patch drivers/common/mlx5/mlx5_prm.h...
Checking patch drivers/common/mlx5/windows/mlx5_win_defs.h...
Checking patch drivers/compress/mlx5/mlx5_compress.c...
Checking patch drivers/crypto/mlx5/mlx5_crypto_gcm.c...
Checking patch drivers/crypto/mlx5/mlx5_crypto_xts.c...
Checking patch drivers/net/mlx5/hws/mlx5dr_send.c...
error: while searching for:
return;
if (unlikely(cqe_opcode != MLX5_CQE_REQ)) {
struct mlx5_err_cqe *err_cqe = (struct mlx5_err_cqe *)cqe;
DR_LOG(ERR, "CQE ERR:0x%x, Vendor_ERR:0x%x, OP:0x%x, QPN:0x%x, WQE_CNT:0x%x",
err_cqe->syndrome, err_cqe->vendor_err_synd, cqe_opcode,
error: patch failed: drivers/net/mlx5/hws/mlx5dr_send.c:599
error: drivers/net/mlx5/hws/mlx5dr_send.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_aso.c...
Checking patch drivers/net/mlx5/mlx5_rx.c...
Checking patch drivers/net/mlx5/mlx5_tx.c...
next parent reply other threads:[~2024-10-03 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241003202605.867419-1-akozyrev@nvidia.com>
2024-10-03 19:58 ` qemudev [this message]
2024-10-03 20:28 ` |SUCCESS| " checkpatch
2024-10-03 20:52 ` |WARNING| pw144997 [PATCH] [v2] " dpdklab
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=202410031958.493Jwdsp3709327@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=akozyrev@nvidia.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).