automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Rongwei Liu <rongweil@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw123790-123792 [PATCH v2 1/5] net/mlx5: adopt IPv6 routing extension prm definition
Date: Mon, 13 Feb 2023 19:30:38 +0800	[thread overview]
Message-ID: <202302131130.31DBUcj63076800@localhost.localdomain> (raw)
In-Reply-To: <20230213113747.3677487-2-rongweil@nvidia.com>

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

_apply patch failure_

Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Mon, 13 Feb 2023 13:37:43 +0200
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: da7cd22e6e518a5e65a70ee666cf5db2c2a3daf7

Apply patch set 123790-123792 failed:

Checking patch drivers/net/mlx5/hws/mlx5dr_definer.c...
Hunk #2 succeeded at 856 (offset -32 lines).
Hunk #3 succeeded at 878 (offset -32 lines).
Hunk #4 succeeded at 886 (offset -32 lines).
Hunk #5 succeeded at 899 (offset -32 lines).
Hunk #6 succeeded at 913 (offset -32 lines).
Hunk #7 succeeded at 924 (offset -32 lines).
Hunk #8 succeeded at 939 (offset -32 lines).
Hunk #9 succeeded at 954 (offset -32 lines).
Hunk #10 succeeded at 970 (offset -32 lines).
Hunk #11 succeeded at 983 (offset -32 lines).
Hunk #12 succeeded at 994 (offset -32 lines).
Hunk #13 succeeded at 1015 (offset -32 lines).
error: while searching for:
	int i, ret;

	cd.fc = fc;
	cd.caps = ctx->caps;
	cd.relaxed = mt->flags & MLX5DR_MATCH_TEMPLATE_FLAG_RELAXED_MATCH;

	/* Collect all RTE fields to the field array and set header layout */

error: patch failed: drivers/net/mlx5/hws/mlx5dr_definer.c:1657
error: drivers/net/mlx5/hws/mlx5dr_definer.c: patch does not apply


       reply	other threads:[~2023-02-13 11:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230213113747.3677487-2-rongweil@nvidia.com>
2023-02-13 11:30 ` qemudev [this message]
2023-02-13 11:40 ` |SUCCESS| pw123790 " 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=202302131130.31DBUcj63076800@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=rongweil@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).