From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122962-122963 [PATCH v10 2/2] ethdev: add quota flow action and item
Date: Fri, 3 Feb 2023 17:06:14 +0800 [thread overview]
Message-ID: <202302030906.31396Ejn1238862@localhost.localdomain> (raw)
In-Reply-To: <20230202134750.10418-2-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122963
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thu, 2 Feb 2023 15:47:49 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 8865a5a6e68b54c298987f07d2604c62eda8bffd
122962-122963 --> 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 prev parent reply other threads:[~2023-02-03 9:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230202134750.10418-2-getelson@nvidia.com>
2023-02-02 13:50 ` |SUCCESS| pw122963 " checkpatch
2023-02-02 16:00 ` 0-day Robot
2023-02-03 9:06 ` qemudev [this message]
2023-02-03 9:10 ` |SUCCESS| pw122962-122963 " qemudev
2023-02-02 14:26 |SUCCESS| pw122962-122963 [PATCH] [v10, " dpdklab
2023-02-02 14:39 dpdklab
2023-02-02 14:46 dpdklab
2023-02-02 15:07 dpdklab
2023-02-02 15:17 dpdklab
2023-02-02 15:23 dpdklab
2023-02-02 15:29 dpdklab
2023-02-02 15:49 dpdklab
2023-02-02 16:42 dpdklab
2023-02-03 12:52 dpdklab
2023-02-03 14:34 dpdklab
2023-02-03 14:34 dpdklab
2023-02-03 14:35 dpdklab
2023-02-03 14:35 dpdklab
2023-02-03 14:36 dpdklab
2023-02-03 14:36 dpdklab
2023-02-03 14:36 dpdklab
2023-02-04 9:28 dpdklab
2023-02-04 20:45 dpdklab
2023-02-04 21: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=202302030906.31396Ejn1238862@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).