From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122361-122362 [PATCH v6 2/2] ethdev: add quota flow action and item
Date: Fri, 20 Jan 2023 00:42:04 +0800 [thread overview]
Message-ID: <202301191642.30JGg4Zw2928245@localhost.localdomain> (raw)
In-Reply-To: <20230119164713.7164-2-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122362
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thu, 19 Jan 2023 18:47:12 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: f2ea2a08e57f7aa539140d08973c908503abf969
122361-122362 --> 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-19 16:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230119164713.7164-2-getelson@nvidia.com>
2023-01-19 16:42 ` qemudev [this message]
2023-01-19 16:46 ` qemudev
2023-01-19 16:48 ` |SUCCESS| pw122362 " checkpatch
2023-01-19 18:19 ` 0-day Robot
2023-01-20 17:10 |SUCCESS| pw122361-122362 [PATCH] [v6, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-20 12:42 dpdklab
2023-01-20 2:32 dpdklab
2023-01-20 2:32 dpdklab
2023-01-20 2:30 dpdklab
2023-01-20 2:29 dpdklab
2023-01-20 2:29 dpdklab
2023-01-20 2:28 dpdklab
2023-01-20 2:28 dpdklab
2023-01-20 2:28 dpdklab
2023-01-20 0:34 dpdklab
2023-01-19 19:14 dpdklab
2023-01-19 17:41 dpdklab
2023-01-19 17:36 dpdklab
2023-01-19 17:29 dpdklab
2023-01-19 17:27 dpdklab
2023-01-19 17:26 dpdklab
2023-01-19 17:24 dpdklab
2023-01-19 17:21 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=202301191642.30JGg4Zw2928245@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).