automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Maayan Kashani <mkashani@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw156165-156167 [PATCH 1/4] net/mlx5: add driver event callbacks
Date: Tue, 26 Aug 2025 19:12:28 +0800	[thread overview]
Message-ID: <202508261112.57QBCS991970881@localhost.localdomain> (raw)
In-Reply-To: <20250826114556.10068-2-mkashani@nvidia.com>

Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/156165

_apply patch failure_

Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Tue, 26 Aug 2025 14:45:52 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 507dd6a18ebcae562fd0539bddbf499a4b891bb7

Apply patch set 156165-156167 failed:

Checking patch drivers/net/mlx5/mlx5_flow.c...
Hunk #1 succeeded at 8159 (offset -6 lines).
Hunk #2 succeeded at 8172 (offset -6 lines).
error: while searching for:
mlx5_flow_start_default(struct rte_eth_dev *dev)
{
	struct rte_flow_error error;
#ifdef HAVE_MLX5_HWS_SUPPORT
	struct mlx5_priv *priv = dev->data->dev_private;

	if (priv->sh->config.dv_flow_en == 2) {
		/*
		 * Ignore this failure, if the proxy port is not started, other
		 * default jump actions are not created and this rule will not

error: patch failed: drivers/net/mlx5/mlx5_flow.c:8220
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow.h...
Checking patch drivers/net/mlx5/mlx5_trigger.c...
Checking patch drivers/net/mlx5/rte_pmd_mlx5.h...


       reply	other threads:[~2025-08-26 11:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250826114556.10068-2-mkashani@nvidia.com>
2025-08-26 11:12 ` qemudev [this message]
2025-08-26 11:45 ` |WARNING| pw156165 " 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=202508261112.57QBCS991970881@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=mkashani@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).