From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122465-122466 [PATCH v7 2/2] ethdev: add quota flow action and item
Date: Tue, 24 Jan 2023 17:32:02 +0800 [thread overview]
Message-ID: <202301240932.30O9W2vk4193049@localhost.localdomain> (raw)
In-Reply-To: <20230124093750.2472-2-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122466
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tue, 24 Jan 2023 11:37:49 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: f2ea2a08e57f7aa539140d08973c908503abf969
122465-122466 --> 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:[~2023-01-24 9:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230124093750.2472-2-getelson@nvidia.com>
2023-01-24 9:32 ` qemudev [this message]
2023-01-24 9:35 ` qemudev
2023-01-24 9:39 ` |SUCCESS| pw122466 " checkpatch
2023-01-24 10:59 ` 0-day Robot
2023-01-25 3:28 |SUCCESS| pw122465-122466 [PATCH] [v7, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-24 22:26 dpdklab
2023-01-24 22:16 dpdklab
2023-01-24 20:58 dpdklab
2023-01-24 20:54 dpdklab
2023-01-24 19:17 dpdklab
2023-01-24 13:06 dpdklab
2023-01-24 12:57 dpdklab
2023-01-24 12:57 dpdklab
2023-01-24 12:55 dpdklab
2023-01-24 12:55 dpdklab
2023-01-24 12:55 dpdklab
2023-01-24 12:54 dpdklab
2023-01-24 11:51 dpdklab
2023-01-24 10:31 dpdklab
2023-01-24 10:27 dpdklab
2023-01-24 10:20 dpdklab
2023-01-24 10:11 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=202301240932.30O9W2vk4193049@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).