automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>, zhoumin@loongson.cn
Subject: |WARNING| pw133667 [PATCH v2] net/mlx5: add global API prefix to public constants
Date: Tue, 31 Oct 2023 21:20:21 +0800	[thread overview]
Message-ID: <202310311320.39VDKLaJ4051951@localhost.localdomain> (raw)
In-Reply-To: <20231031133852.509136-1-thomas@monjalon.net>

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

_apply patch failure_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Tue, 31 Oct 2023 14:38:10 +0100
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 441197cc1ab413c379a88abbcf8e98b195c8eb76

Apply patch set 133667 failed:

Checking patch doc/guides/nics/mlx5.rst...
Hunk #2 succeeded at 2216 (offset 31 lines).
Checking patch drivers/net/mlx5/mlx5.h...
Hunk #1 succeeded at 1697 (offset 13 lines).
Hunk #2 succeeded at 1848 (offset 12 lines).
Checking patch drivers/net/mlx5/mlx5_defs.h...
Checking patch drivers/net/mlx5/mlx5_ethdev.c...
Checking patch drivers/net/mlx5/mlx5_flow.c...
Hunk #1 succeeded at 192 (offset -5 lines).
Hunk #2 succeeded at 7724 (offset 11 lines).
Hunk #3 succeeded at 7798 (offset 11 lines).
Hunk #4 succeeded at 7861 (offset 11 lines).
Hunk #5 succeeded at 7869 (offset 11 lines).
Hunk #6 succeeded at 7905 (offset 11 lines).
Hunk #7 succeeded at 7916 (offset 11 lines).
Hunk #8 succeeded at 7930 (offset 11 lines).
Hunk #9 succeeded at 8004 (offset 11 lines).
Hunk #10 succeeded at 8074 (offset 11 lines).
Hunk #11 succeeded at 8544 (offset -12 lines).
Checking patch drivers/net/mlx5/mlx5_flow.h...
error: while searching for:
	case RTE_FLOW_ITEM_TYPE_METER_COLOR:
		return mlx5_flow_hw_aso_tag;
	case RTE_FLOW_ITEM_TYPE_TAG:
		if (id == MLX5_LINEAR_HASH_TAG_INDEX)
			return REG_C_3;
		MLX5_ASSERT(id < MLX5_FLOW_HW_TAGS_MAX);
		return mlx5_flow_hw_avl_tags[id];

error: patch failed: drivers/net/mlx5/mlx5_flow.h:1702
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
error: while searching for:
			uint8_t tag_index = flow_tag_index_get(data);
			int reg;

			off_be = (tag_index == MLX5_LINEAR_HASH_TAG_INDEX) ?
				 16 - (data->offset + width) + 16 : data->offset;
			if (priv->sh->config.dv_flow_en == 2)
				reg = flow_hw_get_reg_id(RTE_FLOW_ITEM_TYPE_TAG,

error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:1916
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 1189 (offset 113 lines).
Hunk #2 succeeded at 2633 (offset 244 lines).
Checking patch drivers/net/mlx5/mlx5_rx.c...
Checking patch drivers/net/mlx5/mlx5_rx.h...
Checking patch drivers/net/mlx5/mlx5_rxq.c...
Checking patch drivers/net/mlx5/mlx5_testpmd.c...
Checking patch drivers/net/mlx5/rte_pmd_mlx5.h...


       reply	other threads:[~2023-10-31 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231031133852.509136-1-thomas@monjalon.net>
2023-10-31 13:20 ` qemudev [this message]
2023-10-31 13:40 ` |SUCCESS| " checkpatch
2023-10-31 14:00 |WARNING| pw133667 [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=202310311320.39VDKLaJ4051951@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).