From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Gregory Etelson <getelson@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw133574-133603 [PATCH 01/30] net/mlx5/hws: Definer, add mlx5dr context to definer_conv_data
Date: Mon, 30 Oct 2023 00:21:25 +0800 [thread overview]
Message-ID: <202310291621.39TGLPfs2611611@localhost.localdomain> (raw)
In-Reply-To: <20231029163202.216450-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/133574
_apply patch failure_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Sun, 29 Oct 2023 18:31:33 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 8fa22e1f79aae7dfc7a9eb77034e555e155e5e2a
Apply patch set 133574-133603 failed:
Checking patch drivers/net/mlx5/mlx5_flow.c...
Hunk #1 succeeded at 1638 (offset -80 lines).
Checking patch drivers/net/mlx5/mlx5_flow.h...
Hunk #1 succeeded at 1632 (offset -46 lines).
Hunk #2 succeeded at 1679 (offset -46 lines).
error: while searching for:
}
void
mlx5_indirect_list_handles_release(struct rte_eth_dev *dev);
#ifdef HAVE_MLX5_HWS_SUPPORT
struct mlx5_mirror;
void
error: patch failed: drivers/net/mlx5/mlx5_flow.h:2874
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
Checking patch drivers/net/mlx5/mlx5_flow_hw.c...
Hunk #1 succeeded at 5275 (offset -320 lines).
Hunk #2 succeeded at 5334 (offset -320 lines).
next parent reply other threads:[~2023-10-29 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231029163202.216450-1-getelson@nvidia.com>
2023-10-29 16:21 ` qemudev [this message]
2023-10-29 16:34 ` |SUCCESS| pw133574 " checkpatch
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=202310291621.39TGLPfs2611611@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=getelson@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).