From: sys_stv@intel.com
To: test-report@dpdk.org, suanmingm@nvidia.com
Subject: compilation|WARNING| pw(151985) sid(34703) job(PER_PATCH_BUILD15071)[3/3] net/mlx5: allow FDB RSS
Date: 24 Feb 2025 16:58:28 -0800 [thread overview]
Message-ID: <330255$3jr7uu@orviesa005-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2785 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/151985
_apply issues_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: 2025-02-25 00:45:27
Reply_mail: <20250225004527.2066812-4-suanmingm@nvidia.com>
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: 61fc05f1c6a079c0b25b27d1668450134a784d56
Repo:dpdk, CommitID: fab31a03ba98e7457284df95dd9eef2223a4ccaa
* Repo: dpdk-next-net-mlx
Thus the one (rte_flow_error_set) within the goto statement `err`
at the end of __flow_hw_translate_actions_template function may be
redundant for those failed cases. As a result, the error messages
would all be overwritten as "fail to create rte table", making it
displayed at quite large granularity.
--
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: drivers/common/mlx5/mlx5_devx_cmds.c:1352
error: drivers/common/mlx5/mlx5_devx_cmds.c: patch does not apply
error: patch failed: drivers/common/mlx5/mlx5_devx_cmds.h:326
error: drivers/common/mlx5/mlx5_devx_cmds.h: patch does not apply
error: patch failed: drivers/net/mlx5/linux/mlx5_os.c:1718
error: drivers/net/mlx5/linux/mlx5_os.c: patch does not apply
error: patch failed: drivers/net/mlx5/mlx5.h:1987
error: drivers/net/mlx5/mlx5.h: patch does not apply
error: patch failed: drivers/net/mlx5/mlx5_flow_hw.c:9342
error: drivers/net/mlx5/mlx5_flow_hw.c: patch does not apply
Applying: net/mlx5/hws: support jump FDB Rx
Applying: net/mlx5: add jump FDB Rx flag
Patch failed at 0002 net/mlx5: add jump FDB Rx flag
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
* Repo: dpdk
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: drivers/net/mlx5/hws/mlx5dr_cmd.c:1280
error: drivers/net/mlx5/hws/mlx5dr_cmd.c: patch does not apply
error: patch failed: drivers/net/mlx5/hws/mlx5dr_cmd.h:250
error: drivers/net/mlx5/hws/mlx5dr_cmd.h: patch does not apply
error: patch failed: drivers/net/mlx5/hws/mlx5dr_context.h:75
error: drivers/net/mlx5/hws/mlx5dr_context.h: patch does not apply
Applying: net/mlx5/hws: support jump FDB Rx
Patch failed at 0001 net/mlx5/hws: support jump FDB Rx
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
reply other threads:[~2025-02-25 0:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='330255$3jr7uu@orviesa005-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=suanmingm@nvidia.com \
--cc=test-report@dpdk.org \
/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).