From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Ori Kam <orika@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw136641-136644 [PATCH v4 1/4] ethdev: introduce encap hash calculation
Date: Tue, 13 Feb 2024 21:54:53 +0800 [thread overview]
Message-ID: <202402131354.41DDsrDT3465568@localhost.localdomain> (raw)
In-Reply-To: <20240213141640.19812-1-orika@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/136641
_apply patch failure_
Submitter: Ori Kam <orika@nvidia.com>
Date: Tue, 13 Feb 2024 16:16:37 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 7c75d453b719989092e0a53f0c049dc6c247bec0
Apply patch set 136641-136644 failed:
Checking patch doc/guides/prog_guide/rte_flow.rst...
Checking patch doc/guides/rel_notes/release_24_03.rst...
error: while searching for:
* Added HW steering support for modify field ``RTE_FLOW_FIELD_GENEVE_OPT_CLASS`` flow action.
* Added HW steering support for modify field ``RTE_FLOW_FIELD_GENEVE_OPT_DATA`` flow action.
Removed Items
-------------
error: patch failed: doc/guides/rel_notes/release_24_03.rst:102
error: doc/guides/rel_notes/release_24_03.rst: patch does not apply
Checking patch lib/ethdev/rte_flow.c...
error: while searching for:
hash, error);
return flow_err(port_id, ret, error);
}
error: patch failed: lib/ethdev/rte_flow.c:2484
error: lib/ethdev/rte_flow.c: patch does not apply
Checking patch lib/ethdev/rte_flow.h...
Checking patch lib/ethdev/rte_flow_driver.h...
Hunk #1 succeeded at 252 (offset -118 lines).
Checking patch lib/ethdev/version.map...
error: while searching for:
# added in 24.03
rte_eth_find_rss_algo;
};
INTERNAL {
error: patch failed: lib/ethdev/version.map:319
error: lib/ethdev/version.map: patch does not apply
next parent reply other threads:[~2024-02-13 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240213141640.19812-1-orika@nvidia.com>
2024-02-13 13:54 ` qemudev [this message]
2024-02-13 14:18 ` |SUCCESS| pw136641 " checkpatch
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=202402131354.41DDsrDT3465568@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=orika@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).