From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121834-121835 [PATCH v3 2/2] ethdev: add quota flow action and item
Date: Wed, 11 Jan 2023 20:17:45 +0800 [thread overview]
Message-ID: <202301111217.30BCHjB92341182@localhost.localdomain> (raw)
In-Reply-To: <20230111122006.13818-2-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121835
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Wed, 11 Jan 2023 14:20:05 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7f6b150cb79dad10b82fe004e5b2310e39507381
121834-121835 --> 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-11 12:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230111122006.13818-2-getelson@nvidia.com>
2023-01-11 12:17 ` qemudev [this message]
2023-01-11 12:21 ` |SUCCESS| pw121835 " checkpatch
2023-01-11 12:21 ` |SUCCESS| pw121834-121835 " qemudev
2023-01-11 13:39 ` |SUCCESS| pw121835 " 0-day Robot
2023-01-11 12:52 |SUCCESS| pw121834-121835 [PATCH] [v3, " dpdklab
2023-01-11 12:58 dpdklab
2023-01-11 13:00 dpdklab
2023-01-11 13:08 dpdklab
2023-01-11 13:14 dpdklab
2023-01-11 13:20 dpdklab
2023-01-11 13:28 dpdklab
2023-01-11 15:20 dpdklab
2023-01-11 17:21 dpdklab
2023-01-11 17:31 dpdklab
2023-01-11 20:09 dpdklab
2023-01-11 20:10 dpdklab
2023-01-11 20:10 dpdklab
2023-01-11 20:11 dpdklab
2023-01-11 20:11 dpdklab
2023-01-11 20:12 dpdklab
2023-01-11 20:12 dpdklab
2023-01-11 20:13 dpdklab
2023-01-11 20:51 dpdklab
2023-01-11 21:37 dpdklab
2023-01-11 21:40 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=202301111217.30BCHjB92341182@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).