From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Bing Zhao <bingz@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw129152 [PATCH v2] net/mlx5: fix the error set in control tables create
Date: Fri, 30 Jun 2023 17:21:09 +0800 [thread overview]
Message-ID: <202306300921.35U9L9uu1424931@localhost.localdomain> (raw)
In-Reply-To: <20230630092551.434020-1-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/129152
_apply patch failure_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Fri, 30 Jun 2023 12:25:51 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: f95b4da66528b97e7fa44f3503a34c193b2efb44
Apply patch set 129152 failed:
Checking patch drivers/net/mlx5/mlx5_flow_hw.c...
Hunk #2 succeeded at 6233 (offset -9 lines).
Hunk #3 succeeded at 6271 (offset -9 lines).
Hunk #4 succeeded at 6284 (offset -9 lines).
Hunk #5 succeeded at 6325 (offset -9 lines).
Hunk #6 succeeded at 6335 (offset -9 lines).
Hunk #7 succeeded at 6362 (offset -9 lines).
Hunk #8 succeeded at 6372 (offset -9 lines).
Hunk #9 succeeded at 6401 (offset -9 lines).
Hunk #10 succeeded at 6413 (offset -9 lines).
Hunk #11 succeeded at 6488 (offset -9 lines).
Hunk #12 succeeded at 6500 (offset -9 lines).
Hunk #13 succeeded at 6539 (offset -9 lines).
Hunk #14 succeeded at 6549 (offset -9 lines).
Hunk #15 succeeded at 6587 (offset -9 lines).
Hunk #16 succeeded at 6596 (offset -9 lines).
Hunk #17 succeeded at 6669 (offset -9 lines).
Hunk #18 succeeded at 6684 (offset -9 lines).
Hunk #19 succeeded at 6693 (offset -9 lines).
Hunk #20 succeeded at 6711 (offset -9 lines).
Hunk #21 succeeded at 6725 (offset -9 lines).
Hunk #22 succeeded at 6734 (offset -9 lines).
Hunk #23 succeeded at 6752 (offset -9 lines).
Hunk #24 succeeded at 6764 (offset -9 lines).
Hunk #25 succeeded at 6773 (offset -9 lines).
Hunk #26 succeeded at 6788 (offset -9 lines).
Hunk #27 succeeded at 6802 (offset -9 lines).
Hunk #28 succeeded at 6811 (offset -9 lines).
Hunk #29 succeeded at 6829 (offset -9 lines).
Hunk #30 succeeded at 6838 (offset -9 lines).
Hunk #31 succeeded at 6858 (offset -9 lines).
Hunk #32 succeeded at 6987 (offset -9 lines).
error: while searching for:
NULL, "Failed to create vport actions.");
goto err;
}
ret = flow_hw_create_ctrl_tables(dev);
if (ret) {
rte_errno = -ret;
goto err;
}
}
if (!priv->shared_host)
flow_hw_create_send_to_kernel_actions(priv);
error: patch failed: drivers/net/mlx5/mlx5_flow_hw.c:7834
error: drivers/net/mlx5/mlx5_flow_hw.c: patch does not apply
next parent reply other threads:[~2023-06-30 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230630092551.434020-1-bingz@nvidia.com>
2023-06-30 9:21 ` qemudev [this message]
2023-06-30 9:26 ` 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=202306300921.35U9L9uu1424931@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=bingz@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).