From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137459 [PATCH v5] app/testpmd: support updating flow rule actions
Date: Thu, 29 Feb 2024 09:50:00 +0800 [thread overview]
Message-ID: <202402290150.41T1o0eI1592553@localhost.localdomain> (raw)
In-Reply-To: <20240229021511.5850-1-okl-plv@napatech.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137459
_Compilation OK_
Submitter: Oleksandr Kolomeiets <okl-plv@napatech.com>
Date: Thu, 29 Feb 2024 03:15:11 +0100
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: f60df26faa3c90fc66d356e16347acd046971441
137459 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next parent reply other threads:[~2024-02-29 2:14 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229021511.5850-1-okl-plv@napatech.com>
2024-02-29 1:50 ` qemudev [this message]
2024-02-29 1:54 ` qemudev
2024-02-29 2:14 ` checkpatch
2024-02-29 3:02 ` |SUCCESS| pw137459 [PATCH] [v5] app/testpmd: support updating flow r dpdklab
2024-02-29 3:02 ` dpdklab
2024-02-29 3:02 ` dpdklab
2024-02-29 3:03 ` dpdklab
2024-02-29 3:03 ` dpdklab
2024-02-29 3:03 ` dpdklab
2024-02-29 3:04 ` dpdklab
2024-02-29 3:04 ` dpdklab
2024-02-29 3:04 ` dpdklab
2024-02-29 3:04 ` dpdklab
2024-02-29 3:04 ` dpdklab
2024-02-29 3:05 ` |SUCCESS| pw137459 [PATCH v5] app/testpmd: support updating flow rule actions 0-day Robot
2024-02-29 3:05 ` |SUCCESS| pw137459 [PATCH] [v5] app/testpmd: support updating flow r dpdklab
2024-02-29 3:05 ` dpdklab
2024-02-29 3:05 ` dpdklab
2024-02-29 3:05 ` dpdklab
2024-02-29 3:06 ` dpdklab
2024-02-29 3:06 ` dpdklab
2024-02-29 3:06 ` dpdklab
2024-02-29 3:07 ` dpdklab
2024-02-29 3:07 ` dpdklab
2024-02-29 3:07 ` dpdklab
2024-02-29 3:07 ` dpdklab
2024-02-29 3:08 ` dpdklab
2024-02-29 3:08 ` dpdklab
2024-02-29 3:08 ` dpdklab
2024-02-29 3:08 ` dpdklab
2024-02-29 3:09 ` dpdklab
2024-02-29 3:09 ` dpdklab
2024-02-29 3:10 ` dpdklab
2024-02-29 3:10 ` dpdklab
2024-02-29 3:11 ` dpdklab
2024-02-29 3:11 ` dpdklab
2024-02-29 3:11 ` dpdklab
2024-02-29 3:12 ` dpdklab
2024-02-29 3:12 ` dpdklab
2024-02-29 3:13 ` dpdklab
2024-02-29 3:13 ` dpdklab
2024-02-29 3:13 ` dpdklab
2024-02-29 3:14 ` dpdklab
2024-02-29 3:16 ` dpdklab
2024-02-29 3:16 ` dpdklab
2024-02-29 3:16 ` dpdklab
2024-02-29 3:17 ` dpdklab
2024-02-29 3:18 ` dpdklab
2024-02-29 3:18 ` dpdklab
2024-02-29 3:18 ` dpdklab
2024-02-29 3:19 ` dpdklab
2024-02-29 3:20 ` dpdklab
2024-02-29 3:20 ` dpdklab
2024-02-29 3:20 ` dpdklab
2024-02-29 3:21 ` dpdklab
2024-02-29 3:21 ` dpdklab
2024-02-29 3:21 ` dpdklab
2024-02-29 3:22 ` dpdklab
2024-02-29 3:22 ` dpdklab
2024-02-29 3:22 ` dpdklab
2024-02-29 3:23 ` dpdklab
2024-02-29 3:23 ` dpdklab
2024-02-29 3:31 ` dpdklab
2024-02-29 3:32 ` dpdklab
2024-02-29 3:35 ` dpdklab
2024-02-29 3:36 ` dpdklab
2024-02-29 3:55 ` dpdklab
2024-02-29 4:26 ` dpdklab
2024-03-01 2:22 ` dpdklab
2024-03-01 2:33 ` dpdklab
2024-03-01 2:44 ` dpdklab
2024-03-01 2:47 ` dpdklab
2024-03-01 21:14 ` dpdklab
2024-03-02 11:51 ` dpdklab
2024-03-02 12:23 ` dpdklab
2024-03-02 12:56 ` 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=202402290150.41T1o0eI1592553@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=test-report@dpdk.org \
/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).