From: sys_stv@intel.com
To: test-report@dpdk.org, dkozlyuk@oss.nvidia.com
Subject: [dpdk-test-report] |WARNING| pw(102530) sid(19868) job(PER_PATCH_BUILD9028)[v4, 3/6] net: advertise no support for keeping flow rules
Date: 21 Oct 2021 21:39:14 -0700 [thread overview]
Message-ID: <746b4b$eohjt2@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2067 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/102530
_apply issues_
Submitter: Dmitry Kozlyuk <dkozlyuk@oss.nvidia.com>
Date: 2021-10-21 06:35:00
Reply_mail: 20211021063503.3632732-4-dkozlyuk@nvidia.com
DPDK git baseline:
Repo:dpdk-next-net, CommitID: 417778d354be36910b7ce58c275122bd19dde29a
Repo:dpdk, CommitID: a188277d5357dd3c7957070650aaac0027bf69dd
* Repo: dpdk-next-net
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-prc.intel.com
Starting new HTTP connection (1): proxy-prc.intel.com
error: patch failed: lib/ethdev/rte_ethdev.h:1445
error: lib/ethdev/rte_ethdev.h: patch does not apply
Applying: ethdev: add capability to keep flow rules on restart
Patch failed at 0001 ethdev: add capability to keep flow rules on restart
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
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-prc.intel.com
Starting new HTTP connection (1): proxy-prc.intel.com
error: patch failed: drivers/net/mlx5/linux/mlx5_os.c:1809
error: drivers/net/mlx5/linux/mlx5_os.c: patch does not apply
error: patch failed: drivers/net/mlx5/mlx5_devx.c:226
error: drivers/net/mlx5/mlx5_devx.c: patch does not apply
Applying: ethdev: add capability to keep flow rules on restart
Applying: ethdev: add capability to keep shared objects on restart
Applying: net: advertise no support for keeping flow rules
Applying: net/mlx5: discover max flow priority using DevX
Applying: net/mlx5: create drop queue using DevX
Patch failed at 0005 net/mlx5: create drop queue using DevX
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
next reply other threads:[~2021-10-22 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 4:39 sys_stv [this message]
2021-10-22 7:31 sys_stv
2021-10-22 7:38 sys_stv
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='746b4b$eohjt2@orsmga008-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dkozlyuk@oss.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).