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| pw140825-140835 [PATCH v5 01/11] net/mlx5: initial design of non template to hws
Date: Thu, 6 Jun 2024 20:12:54 +0800	[thread overview]
Message-ID: <202406061212.456CCsuA268146@localhost.localdomain> (raw)
In-Reply-To: <20240606123256.177947-1-mkashani@nvidia.com>

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

_apply patch failure_

Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Thu, 6 Jun 2024 15:32:46 +0300
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 76cef1af8bdaeaf67a5c4ca5df3f221df994dc46

Apply patch set 140825-140835 failed:

Checking patch drivers/net/mlx5/linux/mlx5_os.c...
Hunk #2 succeeded at 1068 (offset -12 lines).
Hunk #3 succeeded at 1541 (offset -21 lines).
Checking patch drivers/net/mlx5/mlx5.h...
Hunk #1 succeeded at 2293 (offset -34 lines).
Checking patch drivers/net/mlx5/mlx5_flow.c...
Hunk #1 succeeded at 4929 (offset -55 lines).
Hunk #2 succeeded at 5059 (offset -55 lines).
Hunk #3 succeeded at 5153 (offset -55 lines).
Hunk #4 succeeded at 7243 (offset -55 lines).
Hunk #5 succeeded at 7295 (offset -55 lines).
Hunk #6 succeeded at 7476 (offset -55 lines).
Hunk #7 succeeded at 7540 (offset -55 lines).
Hunk #8 succeeded at 7608 (offset -55 lines).
Hunk #9 succeeded at 7749 (offset -55 lines).
Hunk #10 succeeded at 7771 (offset -55 lines).
Hunk #11 succeeded at 7785 (offset -55 lines).
Hunk #12 succeeded at 7920 (offset -55 lines).
Hunk #13 succeeded at 7940 (offset -55 lines).
Hunk #14 succeeded at 7986 (offset -55 lines).
Hunk #15 succeeded at 8017 (offset -55 lines).
Hunk #16 succeeded at 8065 (offset -55 lines).
Hunk #17 succeeded at 8337 (offset -55 lines).
Hunk #18 succeeded at 8427 (offset -55 lines).
Hunk #19 succeeded at 8502 (offset -55 lines).
Hunk #20 succeeded at 8531 (offset -55 lines).
Hunk #21 succeeded at 9843 (offset -56 lines).
Hunk #22 succeeded at 12067 (offset -56 lines).
Checking patch drivers/net/mlx5/mlx5_flow.h...
Hunk #1 succeeded at 620 (offset -5 lines).
Hunk #2 succeeded at 1307 (offset -5 lines).
Hunk #3 succeeded at 1609 (offset -5 lines).
Hunk #4 succeeded at 2112 (offset -88 lines).
Hunk #5 succeeded at 2488 (offset -89 lines).
Hunk #6 succeeded at 3106 (offset -159 lines).
Hunk #7 succeeded at 3159 (offset -159 lines).
Hunk #8 succeeded at 3268 (offset -159 lines).
Hunk #9 succeeded at 3317 (offset -159 lines).
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
Hunk #1 succeeded at 7622 (offset -49 lines).
error: while searching for:
								error);
			if (ret < 0)
				return ret;
			break;
		case MLX5_RTE_FLOW_ITEM_TYPE_TUNNEL:
			/* tunnel offload item was processed before

error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:8115
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_hw.c...
Hunk #1 succeeded at 256 (offset -15 lines).
Hunk #2 succeeded at 4862 (offset -14 lines).
Hunk #3 succeeded at 4885 (offset -14 lines).
Hunk #4 succeeded at 4909 (offset -14 lines).
Hunk #5 succeeded at 7128 (offset -288 lines).
Hunk #6 succeeded at 8034 (offset -593 lines).
Hunk #7 succeeded at 8074 (offset -593 lines).
Hunk #8 succeeded at 8124 (offset -593 lines).
Hunk #9 succeeded at 10400 (offset -593 lines).
Hunk #10 succeeded at 10548 (offset -593 lines).
Hunk #11 succeeded at 12000 (offset -605 lines).
Hunk #12 succeeded at 13386 (offset -607 lines).
Checking patch drivers/net/mlx5/mlx5_flow_verbs.c...
Hunk #1 succeeded at 2183 (offset -3 lines).
Checking patch drivers/net/mlx5/mlx5_trigger.c...
Checking patch drivers/net/mlx5/windows/mlx5_os.c...


       reply	other threads:[~2024-06-06 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240606123256.177947-1-mkashani@nvidia.com>
2024-06-06 12:12 ` qemudev [this message]
2024-06-06 12:35 ` |SUCCESS| pw140825 " 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=202406061212.456CCsuA268146@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).