From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147582 [PATCH] net/mlx5: fix PMD compilation in non-HWS setup
Date: Tue, 29 Oct 2024 21:17:02 +0800 [thread overview]
Message-ID: <202410291317.49TDH2Bf749058@localhost.localdomain> (raw)
In-Reply-To: <20241029133415.583413-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147582
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tue, 29 Oct 2024 15:34:14 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 71c6d89b56ab044d7bdf2a93f242d0a149d171cf
147582 --> 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-10-29 13:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241029133415.583413-1-getelson@nvidia.com>
2024-10-29 13:17 ` qemudev [this message]
2024-10-29 13:21 ` qemudev
2024-10-29 13:35 ` checkpatch
2024-10-30 5:26 ` |SUCCESS| pw147582 [PATCH] net/mlx5: fix PMD compilation in non-HWS dpdklab
2024-10-30 7:23 ` |PENDING| " dpdklab
2024-10-30 7:24 ` dpdklab
2024-10-30 7:43 ` |SUCCESS| " dpdklab
2024-10-30 7:52 ` dpdklab
2024-10-30 8:16 ` dpdklab
2024-10-30 9:42 ` dpdklab
2024-10-30 9:54 ` dpdklab
2024-10-30 14:37 ` dpdklab
2024-10-30 15:09 ` |PENDING| " dpdklab
2024-10-30 15:14 ` |SUCCESS| " dpdklab
2024-10-30 15:28 ` |PENDING| " dpdklab
2024-10-30 15:45 ` |SUCCESS| " dpdklab
2024-10-30 17:20 ` dpdklab
2024-10-30 17:37 ` |WARNING| " dpdklab
2024-10-30 19:51 ` |SUCCESS| " dpdklab
2024-10-31 22:35 ` dpdklab
2024-11-02 9:59 ` dpdklab
2024-11-02 12:05 ` dpdklab
2024-11-02 12:29 ` dpdklab
2024-11-03 23:26 ` 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=202410291317.49TDH2Bf749058@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).