From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140670 [PATCH] net/mlx5: support jump in meter hierarchy
Date: Tue, 4 Jun 2024 10:28:26 +0800 [thread overview]
Message-ID: <202406040228.4542SQKR2658585@localhost.localdomain> (raw)
In-Reply-To: <20240604025157.1209957-1-shunh@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140670
_Compilation OK_
Submitter: Shun Hao <shunh@nvidia.com>
Date: Tue, 4 Jun 2024 05:51:56 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 2cb74c7eba40eb6ef163fa06420c1d36c714e568
140670 --> 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-06-04 2:57 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240604025157.1209957-1-shunh@nvidia.com>
2024-06-04 2:28 ` qemudev [this message]
2024-06-04 2:33 ` qemudev
2024-06-04 2:53 ` checkpatch
2024-06-04 5:16 ` 0-day Robot
2024-06-04 6:25 ` dpdklab
2024-06-04 6:32 ` dpdklab
2024-06-04 6:34 ` dpdklab
2024-06-04 6:35 ` dpdklab
2024-06-04 6:35 ` dpdklab
2024-06-04 6:47 ` dpdklab
2024-06-04 6:47 ` dpdklab
2024-06-04 6:48 ` dpdklab
2024-06-04 6:48 ` dpdklab
2024-06-04 6:49 ` dpdklab
2024-06-04 6:49 ` dpdklab
2024-06-04 6:49 ` dpdklab
2024-06-04 6:50 ` dpdklab
2024-06-04 6:50 ` dpdklab
2024-06-04 6:51 ` dpdklab
2024-06-04 6:51 ` dpdklab
2024-06-04 6:52 ` dpdklab
2024-06-04 6:54 ` dpdklab
2024-06-04 6:57 ` dpdklab
2024-06-04 7:06 ` dpdklab
2024-06-04 7:07 ` dpdklab
2024-06-04 7:12 ` dpdklab
2024-06-04 7:14 ` dpdklab
2024-06-04 7:18 ` dpdklab
2024-06-04 7:19 ` dpdklab
2024-06-04 7:27 ` dpdklab
2024-06-04 7:33 ` dpdklab
2024-06-04 7:37 ` dpdklab
2024-06-04 7:43 ` dpdklab
2024-06-04 8:07 ` dpdklab
2024-06-04 8:13 ` dpdklab
2024-06-04 8:40 ` dpdklab
2024-06-04 8:56 ` dpdklab
2024-06-04 8:57 ` dpdklab
2024-06-04 8:59 ` dpdklab
2024-06-04 9:03 ` dpdklab
2024-06-04 9:10 ` dpdklab
2024-06-04 9:11 ` dpdklab
2024-06-04 9:25 ` dpdklab
2024-06-04 9:25 ` |FAILURE| " dpdklab
2024-06-04 9:26 ` dpdklab
2024-06-04 9:29 ` dpdklab
2024-06-04 9:43 ` |SUCCESS| " dpdklab
2024-06-04 9:43 ` dpdklab
2024-06-04 9:44 ` |FAILURE| " dpdklab
2024-06-04 9:46 ` dpdklab
2024-06-04 9:47 ` dpdklab
2024-06-04 9:54 ` |SUCCESS| " dpdklab
2024-06-04 9:54 ` |FAILURE| " dpdklab
2024-06-04 9:55 ` dpdklab
2024-06-04 9:57 ` dpdklab
2024-06-04 9:57 ` dpdklab
2024-06-04 9:59 ` dpdklab
2024-06-04 9:59 ` dpdklab
2024-06-04 9:59 ` dpdklab
2024-06-04 10:00 ` |SUCCESS| " dpdklab
2024-06-04 10:00 ` |FAILURE| " dpdklab
2024-06-04 10:05 ` dpdklab
2024-06-04 10:05 ` dpdklab
2024-06-04 10:05 ` dpdklab
2024-06-04 10:05 ` |SUCCESS| " dpdklab
2024-06-04 10:06 ` |FAILURE| " dpdklab
2024-06-04 10:06 ` |SUCCESS| " dpdklab
2024-06-04 10:06 ` |FAILURE| " dpdklab
2024-06-04 10:06 ` |SUCCESS| " dpdklab
2024-06-04 10:07 ` |FAILURE| " dpdklab
2024-06-04 10:07 ` dpdklab
2024-06-04 10:08 ` dpdklab
2024-06-04 10:10 ` dpdklab
2024-06-04 10:13 ` dpdklab
2024-06-04 10:14 ` dpdklab
2024-06-04 10:14 ` dpdklab
2024-06-04 10:14 ` dpdklab
2024-06-04 10:15 ` dpdklab
2024-06-04 10:27 ` dpdklab
2024-06-04 10:28 ` dpdklab
2024-06-04 10:28 ` dpdklab
2024-06-04 10:29 ` dpdklab
2024-06-04 10:29 ` dpdklab
2024-06-04 10:29 ` dpdklab
2024-06-04 10:30 ` dpdklab
2024-06-04 10:31 ` dpdklab
2024-06-04 10:31 ` dpdklab
2024-06-04 10:31 ` dpdklab
2024-06-04 10:34 ` dpdklab
2024-06-04 10:37 ` dpdklab
2024-06-04 10:46 ` dpdklab
2024-06-04 10:57 ` dpdklab
2024-06-04 11:04 ` dpdklab
2024-06-04 11:12 ` dpdklab
2024-06-04 13:03 ` 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=202406040228.4542SQKR2658585@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).