automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Michael Baum <michaelba@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw136141-136142 [PATCH v5 1/2] net/mlx5/hws: add support for random number match
Date: Thu, 25 Jan 2024 20:22:24 +0800	[thread overview]
Message-ID: <202401251222.40PCMOQm3267377@localhost.localdomain> (raw)
In-Reply-To: <20240125123708.571526-2-michaelba@nvidia.com>

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

_apply patch failure_

Submitter: Michael Baum <michaelba@nvidia.com>
Date: Thu, 25 Jan 2024 14:37:07 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 2c4a4e999aae115861fba3ae39da684f66de1146

Apply patch set 136141-136142 failed:

Checking patch drivers/net/mlx5/hws/mlx5dr_definer.c...
Hunk #1 succeeded at 182 (offset -5 lines).
Hunk #2 succeeded at 2174 (offset -27 lines).
Hunk #3 succeeded at 2252 (offset -27 lines).
error: while searching for:
			ret = mlx5dr_definer_conv_item_ptype(&cd, items, i);
			item_flags |= MLX5_FLOW_ITEM_PTYPE;
			break;
		case RTE_FLOW_ITEM_TYPE_VXLAN_GPE:
			ret = mlx5dr_definer_conv_item_vxlan_gpe(&cd, items, i);
			item_flags |= MLX5_FLOW_LAYER_VXLAN_GPE;

error: patch failed: drivers/net/mlx5/hws/mlx5dr_definer.c:2645
error: drivers/net/mlx5/hws/mlx5dr_definer.c: patch does not apply
Checking patch drivers/net/mlx5/hws/mlx5dr_definer.h...
Hunk #1 succeeded at 150 (offset -5 lines).
Hunk #2 succeeded at 408 (offset -5 lines).
Hunk #3 succeeded at 522 (offset -5 lines).
Checking patch drivers/net/mlx5/mlx5_flow.h...


       reply	other threads:[~2024-01-25 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240125123708.571526-2-michaelba@nvidia.com>
2024-01-25 12:22 ` qemudev [this message]
2024-01-25 12:39 ` |SUCCESS| pw136141 " 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=202401251222.40PCMOQm3267377@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=michaelba@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).