From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137467 [PATCH] net/mlx5: fix sync meter processing in HWS setup
Date: Thu, 29 Feb 2024 18:34:24 +0800 [thread overview]
Message-ID: <202402291034.41TAYOdh1831511@localhost.localdomain> (raw)
In-Reply-To: <20240229105614.593391-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137467
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thu, 29 Feb 2024 12:56:14 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: a6a7efc3670133a5a25ce43e318fbbaaaf69b692
137467 --> 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-02-29 10:59 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229105614.593391-1-getelson@nvidia.com>
2024-02-29 10:34 ` qemudev [this message]
2024-02-29 10:38 ` qemudev
2024-02-29 10:57 ` |WARNING| " checkpatch
2024-02-29 11:33 ` |FAILURE| pw137467 [PATCH] net/mlx5: fix sync meter processing in HW dpdklab
2024-02-29 11:34 ` dpdklab
2024-02-29 11:35 ` |SUCCESS| " dpdklab
2024-02-29 11:36 ` |FAILURE| " dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 11:36 ` dpdklab
2024-02-29 11:36 ` |SUCCESS| " dpdklab
2024-02-29 11:37 ` dpdklab
2024-02-29 11:37 ` |FAILURE| " dpdklab
2024-02-29 11:37 ` |SUCCESS| " dpdklab
2024-02-29 11:37 ` |FAILURE| " dpdklab
2024-02-29 11:37 ` |SUCCESS| " dpdklab
2024-02-29 11:38 ` dpdklab
2024-02-29 11:39 ` dpdklab
2024-02-29 11:45 ` |FAILURE| " dpdklab
2024-02-29 11:46 ` |SUCCESS| " dpdklab
2024-02-29 11:46 ` |FAILURE| " dpdklab
2024-02-29 11:46 ` |SUCCESS| " dpdklab
2024-02-29 11:47 ` dpdklab
2024-02-29 11:47 ` dpdklab
2024-02-29 11:47 ` |FAILURE| " dpdklab
2024-02-29 11:47 ` |SUCCESS| " dpdklab
2024-02-29 11:47 ` |FAILURE| " dpdklab
2024-02-29 11:48 ` |SUCCESS| " dpdklab
2024-02-29 11:48 ` dpdklab
2024-02-29 11:48 ` |FAILURE| " dpdklab
2024-02-29 11:48 ` |SUCCESS| " dpdklab
2024-02-29 11:48 ` dpdklab
2024-02-29 11:51 ` dpdklab
2024-02-29 11:51 ` dpdklab
2024-02-29 11:52 ` dpdklab
2024-02-29 11:52 ` |FAILURE| " dpdklab
2024-02-29 11:53 ` |SUCCESS| " dpdklab
2024-02-29 11:53 ` dpdklab
2024-02-29 11:53 ` dpdklab
2024-02-29 11:56 ` dpdklab
2024-02-29 11:57 ` dpdklab
2024-02-29 11:57 ` dpdklab
2024-02-29 11:58 ` dpdklab
2024-02-29 11:58 ` dpdklab
2024-02-29 11:58 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 11:59 ` dpdklab
2024-02-29 12:03 ` dpdklab
2024-02-29 12:04 ` |FAILURE| " dpdklab
2024-02-29 12:04 ` |SUCCESS| " dpdklab
2024-02-29 12:04 ` dpdklab
2024-02-29 12:04 ` dpdklab
2024-02-29 12:04 ` dpdklab
2024-02-29 12:05 ` dpdklab
2024-02-29 12:05 ` dpdklab
2024-02-29 12:06 ` dpdklab
2024-02-29 12:06 ` dpdklab
2024-02-29 12:10 ` dpdklab
2024-02-29 12:10 ` dpdklab
2024-02-29 12:11 ` dpdklab
2024-02-29 12:11 ` dpdklab
2024-02-29 12:12 ` dpdklab
2024-02-29 12:59 ` dpdklab
2024-02-29 13:35 ` dpdklab
2024-03-01 4:53 ` dpdklab
2024-03-01 5:00 ` dpdklab
2024-03-01 5:16 ` dpdklab
2024-03-01 5:21 ` dpdklab
2024-03-02 4:05 ` dpdklab
2024-03-02 17:17 ` dpdklab
2024-03-02 17:50 ` dpdklab
2024-03-02 18:22 ` 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=202402291034.41TAYOdh1831511@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).