From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Rongwei Liu <rongweil@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw126147-126148 [RFC v1 1/2] ethdev: add IPv6 extension push remove action
Date: Mon, 17 Apr 2023 10:15:16 +0800 [thread overview]
Message-ID: <202304170215.33H2FGcV1135351@localhost.localdomain> (raw)
In-Reply-To: <20230417022630.2377505-2-rongweil@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/126147
_apply patch failure_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Mon, 17 Apr 2023 05:26:29 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 40a62da00b3619ed72be6ceeded89d1fe62ed027
Apply patch set 126147-126148 failed:
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:
| ``policy`` | Meter policy object |
+------------------+----------------------+
Negative types
~~~~~~~~~~~~~~
error: patch failed: doc/guides/prog_guide/rte_flow.rst:3308
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/ethdev/rte_flow.c...
error: while searching for:
MK_FLOW_ACTION(SEND_TO_KERNEL, 0),
MK_FLOW_ACTION(QUOTA, sizeof(struct rte_flow_action_quota)),
MK_FLOW_ACTION(INDIRECT_LIST, 0),
};
int
error: patch failed: lib/ethdev/rte_flow.c:272
error: lib/ethdev/rte_flow.c: patch does not apply
Checking patch lib/ethdev/rte_flow.h...
error: while searching for:
* RTE_FLOW_ACTION_TYPE_INDIRECT_LIST
*/
RTE_FLOW_ACTION_TYPE_INDIRECT_LIST,
};
/**
error: patch failed: lib/ethdev/rte_flow.h:3029
error: lib/ethdev/rte_flow.h: patch does not apply
next parent reply other threads:[~2023-04-17 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230417022630.2377505-2-rongweil@nvidia.com>
2023-04-17 2:15 ` qemudev [this message]
2023-04-17 2:28 ` |SUCCESS| pw126147 " 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=202304170215.33H2FGcV1135351@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=rongweil@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).