From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138464 [PATCH] net/mlx5: fix sync meter action
Date: Tue, 19 Mar 2024 01:49:25 +0800 [thread overview]
Message-ID: <202403181749.42IHnPVp2706567@localhost.localdomain> (raw)
In-Reply-To: <20240318181045.272879-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138464
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Mon, 18 Mar 2024 20:10:45 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 478ca87cba284417f4575060ce02d94aa4991307
138464 --> 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-03-18 18:14 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318181045.272879-1-getelson@nvidia.com>
2024-03-18 17:49 ` qemudev [this message]
2024-03-18 17:54 ` qemudev
2024-03-18 18:13 ` checkpatch
2024-03-18 19:03 ` 0-day Robot
2024-03-18 19:32 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:35 ` dpdklab
2024-03-18 19:37 ` dpdklab
2024-03-18 19:37 ` dpdklab
2024-03-18 19:37 ` dpdklab
2024-03-18 19:38 ` dpdklab
2024-03-18 19:38 ` dpdklab
2024-03-18 19:55 ` dpdklab
2024-03-18 19:57 ` dpdklab
2024-03-18 19:57 ` dpdklab
2024-03-18 19:58 ` dpdklab
2024-03-18 19:58 ` dpdklab
2024-03-18 19:59 ` dpdklab
2024-03-18 19:59 ` dpdklab
2024-03-18 20:00 ` dpdklab
2024-03-18 20:00 ` dpdklab
2024-03-18 20:01 ` dpdklab
2024-03-18 20:01 ` dpdklab
2024-03-18 20:01 ` dpdklab
2024-03-18 20:02 ` dpdklab
2024-03-18 20:02 ` dpdklab
2024-03-18 20:02 ` dpdklab
2024-03-18 20:03 ` dpdklab
2024-03-18 20:06 ` dpdklab
2024-03-18 20:09 ` dpdklab
2024-03-18 20:10 ` dpdklab
2024-03-18 20:10 ` dpdklab
2024-03-18 20:14 ` dpdklab
2024-03-18 20:16 ` dpdklab
2024-03-18 20:16 ` dpdklab
2024-03-18 20:16 ` dpdklab
2024-03-18 20:17 ` dpdklab
2024-03-18 20:17 ` dpdklab
2024-03-18 20:17 ` dpdklab
2024-03-18 20:18 ` dpdklab
2024-03-18 20:18 ` dpdklab
2024-03-18 20:18 ` dpdklab
2024-03-18 20:18 ` dpdklab
2024-03-18 20:18 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:20 ` dpdklab
2024-03-18 20:24 ` |FAILURE| " dpdklab
2024-03-18 20:26 ` |SUCCESS| " dpdklab
2024-03-18 20:30 ` dpdklab
2024-03-18 20:31 ` dpdklab
2024-03-18 20:31 ` dpdklab
2024-03-18 20:31 ` |FAILURE| " dpdklab
2024-03-18 20:32 ` |SUCCESS| " dpdklab
2024-03-18 20:32 ` dpdklab
2024-03-18 20:33 ` dpdklab
2024-03-18 20:34 ` |FAILURE| " dpdklab
2024-03-18 20:35 ` |SUCCESS| " dpdklab
2024-03-18 20:35 ` |FAILURE| " dpdklab
2024-03-18 20:36 ` |SUCCESS| " dpdklab
2024-03-18 20:36 ` |FAILURE| " dpdklab
2024-03-18 20:37 ` dpdklab
2024-03-18 20:37 ` |SUCCESS| " dpdklab
2024-03-18 20:37 ` dpdklab
2024-03-18 20:38 ` |FAILURE| " dpdklab
2024-03-18 20:39 ` dpdklab
2024-03-18 20:39 ` |SUCCESS| " dpdklab
2024-03-18 20:40 ` |FAILURE| " dpdklab
2024-03-18 20:40 ` |SUCCESS| " dpdklab
2024-03-18 20:41 ` |FAILURE| " dpdklab
2024-03-18 20:43 ` |SUCCESS| " dpdklab
2024-03-18 20:44 ` |FAILURE| " dpdklab
2024-03-18 20:45 ` |SUCCESS| " dpdklab
2024-03-18 21:20 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 19:16 ` 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=202403181749.42IHnPVp2706567@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).