From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147848 [PATCH] net/ice: enable link speed 200G
Date: Thu, 31 Oct 2024 09:15:23 +0800 [thread overview]
Message-ID: <202410310115.49V1FNqN3494094@localhost.localdomain> (raw)
In-Reply-To: <20241031011819.2020557-1-mingjinx.ye@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147848
_Compilation OK_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Thu, 31 Oct 2024 01:18:19 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 150f1e8b74e41d4f3f7d60eb1a18379345d6a5b3
147848 --> 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-31 1:48 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241031011819.2020557-1-mingjinx.ye@intel.com>
2024-10-31 1:15 ` qemudev [this message]
2024-10-31 1:20 ` qemudev
2024-10-31 1:42 ` |WARNING| " checkpatch
2024-10-31 2:47 ` |SUCCESS| " 0-day Robot
2024-10-31 16:56 ` dpdklab
2024-10-31 17:10 ` dpdklab
2024-10-31 18:00 ` |PENDING| " dpdklab
2024-10-31 18:03 ` dpdklab
2024-10-31 18:40 ` |SUCCESS| " dpdklab
2024-10-31 18:47 ` |PENDING| " dpdklab
2024-10-31 18:52 ` |SUCCESS| " dpdklab
2024-10-31 18:59 ` |PENDING| " dpdklab
2024-10-31 19:00 ` |SUCCESS| " dpdklab
2024-10-31 19:01 ` dpdklab
2024-10-31 19:03 ` dpdklab
2024-10-31 19:10 ` dpdklab
2024-10-31 19:10 ` dpdklab
2024-10-31 19:21 ` dpdklab
2024-10-31 19:21 ` dpdklab
2024-10-31 19:33 ` dpdklab
2024-10-31 20:00 ` dpdklab
2024-10-31 20:09 ` |PENDING| " dpdklab
2024-10-31 20:24 ` |SUCCESS| " dpdklab
2024-10-31 21:03 ` dpdklab
2024-11-01 1:23 ` |PENDING| " dpdklab
2024-11-01 2:00 ` |SUCCESS| " dpdklab
2024-11-01 2:24 ` dpdklab
2024-11-01 3:35 ` dpdklab
2024-11-01 4:02 ` dpdklab
2024-11-01 4:18 ` dpdklab
2024-11-01 5:10 ` dpdklab
2024-11-01 6:24 ` dpdklab
2024-11-01 7:18 ` dpdklab
2024-11-01 9:58 ` dpdklab
2024-11-01 10:34 ` dpdklab
2024-11-01 10:34 ` dpdklab
2024-11-01 16:27 ` dpdklab
2024-11-01 17:08 ` dpdklab
2024-11-01 17:19 ` dpdklab
2024-11-01 17:54 ` dpdklab
2024-11-02 8:02 ` dpdklab
2024-11-02 8:34 ` dpdklab
2024-11-02 18:42 ` dpdklab
2024-11-02 18:46 ` dpdklab
2024-11-02 23:05 ` dpdklab
2024-11-02 23:07 ` dpdklab
2024-11-02 23:12 ` dpdklab
2024-11-02 23:14 ` dpdklab
2024-11-05 13:22 ` dpdklab
2024-11-05 14:15 ` 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=202410310115.49V1FNqN3494094@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).