From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw104239 [PATCH] [v3] net/mlx5: fix the NIC egress flow mismatch in switchdev mode
Date: Fri, 12 Nov 2021 13:09:01 +0000 (UTC) [thread overview]
Message-ID: <20211112130901.6BF2C60711@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/104239
_apply patch failure_
Submitter: Jiawei Wang <jiaweiw@nvidia.com>
Date: Friday, November 12 2021 12:42:35
Applied on: CommitID:19d024003dfce0018c9e52635b78efdc6e1c172a
Apply patch set 104239 failed:
Checking patch doc/guides/nics/mlx5.rst...
error: while searching for:
completions, the scheduled send timestamps should not be specified
with non-zero msb
Statistics
----------
error: patch failed: doc/guides/nics/mlx5.rst:493
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
Hunk #1 succeeded at 7157 (offset -7 lines).
Hunk #2 succeeded at 7994 (offset -7 lines).
Hunk #3 succeeded at 13570 (offset -7 lines).
Applying patch doc/guides/nics/mlx5.rst with 1 reject...
Rejected hunk #1.
Applied patch drivers/net/mlx5/mlx5_flow_dv.c cleanly.
diff a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst (rejected hunks)
@@ -493,6 +493,8 @@ Limitations
completions, the scheduled send timestamps should not be specified
with non-zero msb
+- The NIC Egress flow on representor port is not supported.
+
Statistics
----------
https://lab.dpdk.org/results/dashboard/patchsets/20181/
UNH-IOL DPDK Community Lab
reply other threads:[~2021-11-12 13:09 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=20211112130901.6BF2C60711@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).