From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Shani Peretz <shperetz@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw144703 [PATCH v2] examples/flow_filtering: introduce use cases snippets
Date: Tue, 1 Oct 2024 00:12:24 +0800 [thread overview]
Message-ID: <202409301612.48UGCOqi506064@localhost.localdomain> (raw)
In-Reply-To: <20240930164015.541137-1-shperetz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/144703
_apply patch failure_
Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Mon, 30 Sep 2024 19:40:15 +0300
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: bf0ff8df59c7e32f95c0b542cc4a7918f8a3da84
Apply patch set 144703 failed:
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: doc/guides/prog_guide/rte_flow.rst: No such file or directory
Checking patch doc/guides/sample_app_ug/flow_filtering.rst...
Checking patch examples/flow_filtering/Makefile...
Checking patch examples/flow_filtering/common.h...
Checking patch examples/flow_filtering/flow_blocks.c...
Checking patch examples/flow_filtering/flow_skeleton.c...
Checking patch examples/flow_filtering/main.c...
Checking patch examples/flow_filtering/meson.build...
Checking patch examples/flow_filtering/snippets/snippet_match_gre.c...
Checking patch examples/flow_filtering/snippets/snippet_match_gre.h...
Checking patch examples/flow_filtering/snippets/snippet_match_ipv4.c...
Checking patch examples/flow_filtering/snippets/snippet_match_ipv4.h...
Checking patch examples/flow_filtering/snippets/snippet_match_mpls.c...
Checking patch examples/flow_filtering/snippets/snippet_match_mpls.h...
next parent reply other threads:[~2024-09-30 16:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240930164015.541137-1-shperetz@nvidia.com>
2024-09-30 16:12 ` qemudev [this message]
2024-09-30 16:42 ` |SUCCESS| " checkpatch
2024-09-30 17:44 ` 0-day Robot
2024-09-30 21:32 ` |SUCCESS| pw144703 [PATCH] [v2] examples/flow_filtering: introduce u dpdklab
2024-09-30 21:33 ` dpdklab
2024-09-30 21:40 ` dpdklab
2024-09-30 21:42 ` dpdklab
2024-09-30 21:44 ` dpdklab
2024-09-30 21:48 ` dpdklab
2024-09-30 22:04 ` |PENDING| " dpdklab
2024-09-30 22:31 ` dpdklab
2024-09-30 22:31 ` dpdklab
2024-09-30 22:32 ` |SUCCESS| " dpdklab
2024-09-30 23:27 ` dpdklab
2024-09-30 23:36 ` dpdklab
2024-10-01 0:03 ` dpdklab
2024-10-01 0:16 ` |PENDING| " dpdklab
2024-10-01 0:25 ` |SUCCESS| " dpdklab
2024-10-01 0:31 ` dpdklab
2024-10-01 2:24 ` dpdklab
2024-10-01 2:36 ` dpdklab
2024-10-01 2:58 ` dpdklab
2024-10-01 3:13 ` dpdklab
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=202409301612.48UGCOqi506064@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=shperetz@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).