From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126861 [PATCH v1] net/mlx5: add test for hot upgrade
Date: Tue, 16 May 2023 13:43:32 +0800 [thread overview]
Message-ID: <202305160543.34G5hWCU268216@localhost.localdomain> (raw)
In-Reply-To: <20230516054137.1396922-1-rongweil@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126861
_Compilation OK_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Tue, 16 May 2023 08:41:37 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
126861 --> 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 prev parent reply other threads:[~2023-05-16 5:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230516054137.1396922-1-rongweil@nvidia.com>
2023-05-16 5:42 ` checkpatch
2023-05-16 5:43 ` qemudev [this message]
2023-05-16 5:47 ` qemudev
2023-05-16 6:40 ` 0-day Robot
2023-05-16 6:58 |SUCCESS| pw126861 [PATCH] [v1] " dpdklab
2023-05-16 6:59 dpdklab
2023-05-16 7:03 dpdklab
2023-05-16 7:03 dpdklab
2023-05-16 7:03 dpdklab
2023-05-16 7:03 dpdklab
2023-05-16 7:09 dpdklab
2023-05-16 7:10 dpdklab
2023-05-16 7:21 dpdklab
2023-05-16 7:21 dpdklab
2023-05-16 7:38 dpdklab
2023-05-16 7:41 dpdklab
2023-05-16 7:43 dpdklab
2023-05-16 7:43 dpdklab
2023-05-16 7:44 dpdklab
2023-05-16 7:45 dpdklab
2023-05-16 7:51 dpdklab
2023-05-16 7:51 dpdklab
2023-05-16 7:52 dpdklab
2023-05-16 7:52 dpdklab
2023-05-16 8:04 dpdklab
2023-05-16 8:06 dpdklab
2023-05-16 8:35 dpdklab
2023-05-16 8:35 dpdklab
2023-05-16 17:14 dpdklab
2023-05-16 17:31 dpdklab
2023-05-16 17:38 dpdklab
2023-05-16 17:49 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=202305160543.34G5hWCU268216@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).