From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw155322 [PATCH] net/mlx5: document IP fragment matching limitations
Date: Fri, 18 Jul 2025 19:16:29 +0800 [thread overview]
Message-ID: <202507181116.56IBGT9K3732173@localhost.localdomain> (raw)
In-Reply-To: <20250718115156.1220403-1-dsosnowski@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/155322
_apply patch failure_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Fri, 18 Jul 2025 13:51:56 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 9fe9c0b231c8da5435bfccb1963121b4277f961c
Apply patch set 155322 failed:
Checking patch doc/guides/nics/mlx5.rst...
error: while searching for:
#. IP-in-IP is not supported with :ref:`HW steering <mlx5_hws>`.
. _mlx5_nat64:
error: patch failed: doc/guides/nics/mlx5.rst:3305
error: doc/guides/nics/mlx5.rst: patch does not apply
next parent reply other threads:[~2025-07-18 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250718115156.1220403-1-dsosnowski@nvidia.com>
2025-07-18 11:16 ` qemudev [this message]
2025-07-18 11:52 ` |SUCCESS| " checkpatch
2025-07-18 13:03 ` 0-day Robot
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=202507181116.56IBGT9K3732173@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=dsosnowski@nvidia.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).