From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Ori Kam <orika@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw136189-136192 [PATCH 1/4] ethdev: introduce encap hash calculation
Date: Sun, 28 Jan 2024 17:17:42 +0800 [thread overview]
Message-ID: <202401280917.40S9HgSq3950198@localhost.localdomain> (raw)
In-Reply-To: <20240128093943.4461-2-orika@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/136189
_apply patch failure_
Submitter: Ori Kam <orika@nvidia.com>
Date: Sun, 28 Jan 2024 11:39:39 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 6676a3793b4292baf606092a8e3e14ea67550c58
Apply patch set 136189-136192 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 support for VXLAN-GPE matching in HW Steering flow engine
(``dv_flow_en`` = 2).
Removed Items
-------------
error: patch failed: doc/guides/rel_notes/release_24_03.rst:75
error: doc/guides/rel_notes/release_24_03.rst: patch does not apply
Checking patch lib/ethdev/rte_flow.c...
Checking patch lib/ethdev/rte_flow.h...
Checking patch lib/ethdev/rte_flow_driver.h...
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-01-28 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240128093943.4461-2-orika@nvidia.com>
2024-01-28 9:17 ` qemudev [this message]
2024-01-28 9:41 ` |SUCCESS| pw136189 " 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=202401280917.40S9HgSq3950198@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).