From: sys_stv@intel.com
To: test-report@dpdk.org, mkashani@nvidia.com
Subject: compilation|WARNING| pw(140620) sid(32060) job(PER_PATCH_BUILD12122)[v3, 7/7] net/mlx5/hws: bwc - fix deleting action stes
Date: 05 Jun 2024 03:49:34 -0700 [thread overview]
Message-ID: <303f12$27i1js@smtpauth.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/140620
_apply issues_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: 2024-06-03 10:56:34
Reply_mail: <20240603105635.11124-7-mkashani@nvidia.com>
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: a207de9a356ef890dd858064ee94e15f0841f0e1
Repo:dpdk, CommitID: 76cef1af8bdaeaf67a5c4ca5df3f221df994dc46
* Repo: dpdk-next-net-mlx
error: drivers/net/mlx5/hws/mlx5dr_bwc.c: does not exist in index
Applying: net/mlx5/hws: fix bug in matcher disconnect error flow
Applying: net/mlx5/hws: bwc - make burst threshold dynamic
Patch failed at 0002 net/mlx5/hws: bwc - make burst threshold dynamic
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
error: drivers/net/mlx5/hws/mlx5dr_bwc.c: does not exist in index
Applying: net/mlx5/hws: fix bug in matcher disconnect error flow
Applying: net/mlx5/hws: bwc - make burst threshold dynamic
Patch failed at 0002 net/mlx5/hws: bwc - make burst threshold dynamic
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:[~2024-06-05 10:49 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='303f12$27i1js@smtpauth.intel.com' \
--to=sys_stv@intel.com \
--cc=mkashani@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).