automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, xuemingl@nvidia.com
Subject: compilation|WARNING| pw(129340) sid(28861) job(PER_PATCH_BUILD8281)[v2] net/mlx5: support symmetric RSS hash function
Date: 06 Jul 2023 16:10:30 -0700	[thread overview]
Message-ID: <76a62b$o49q8t@fmsmga003-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2497 bytes --]


Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/129340

_apply issues_

Submitter: Xueming Li <xuemingl@nvidia.com>
Date: 2023-07-06 11:55:57
Reply_mail: <20230706115557.8114-1-xuemingl@nvidia.com>

DPDK git baseline:
	Repo:dpdk-next-net-mlx, CommitID: 7961c10f206b843f7d86b65890fccc0ed56725a7
	Repo:dpdk, CommitID: 5d41169b901858e657a8ae3c2dd445bbd8b5e7e5


* Repo: dpdk-next-net-mlx
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/mlx5.h:1509
error: drivers/net/mlx5/mlx5.h: patch does not apply
error: patch failed: drivers/net/mlx5/mlx5_devx.c:803
error: drivers/net/mlx5/mlx5_devx.c: patch does not apply
error: patch failed: drivers/net/mlx5/mlx5_flow.c:2164
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
error: patch failed: drivers/net/mlx5/mlx5_flow.h:900
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:12006
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
error: patch failed: drivers/net/mlx5/mlx5_flow_hw.c:405
error: drivers/net/mlx5/mlx5_flow_hw.c: patch does not apply
error: patch failed: drivers/net/mlx5/mlx5_rx.h:284
error: drivers/net/mlx5/mlx5_rx.h: patch does not apply
error: patch failed: drivers/net/mlx5/mlx5_rxq.c:2759
error: drivers/net/mlx5/mlx5_rxq.c: patch does not apply
Applying: net/mlx5: support symmetric RSS hash function
Patch failed at 0001 net/mlx5: support symmetric RSS hash function
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/mlx5_flow.c:7275
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
Applying: net/mlx5: support symmetric RSS hash function
Patch failed at 0001 net/mlx5: support symmetric RSS hash function
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:[~2023-07-06 23:10 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='76a62b$o49q8t@fmsmga003-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).