From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140321 [PATCH] r8125: add r8125 ethernet poll mode driver
Date: Mon, 27 May 2024 14:27:41 +0800 [thread overview]
Message-ID: <202405270627.44R6RflF2779111@localhost.localdomain> (raw)
In-Reply-To: <20240527061528.10072-1-howard_wang@realsil.com.cn>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140321
_Compilation OK_
Submitter: Howard Wang <howard_wang@realsil.com.cn>
Date: Mon, 27 May 2024 14:15:28 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 2dbb63594a9a985e2c8639b57f9fcd1468b9de97
140321 --> 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-05-27 6:56 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240527061528.10072-1-howard_wang@realsil.com.cn>
2024-05-27 6:27 ` qemudev [this message]
2024-05-27 6:32 ` qemudev
2024-05-27 6:56 ` |WARNING| " checkpatch
2024-05-27 7:40 ` |SUCCESS| pw140321 [PATCH] r8125: add r8125 ethernet poll mode drive dpdklab
2024-05-27 7:40 ` dpdklab
2024-05-27 7:41 ` dpdklab
2024-05-27 7:42 ` dpdklab
2024-05-27 7:42 ` dpdklab
2024-05-27 7:43 ` dpdklab
2024-05-27 7:43 ` dpdklab
2024-05-27 7:44 ` dpdklab
2024-05-27 7:44 ` |FAILURE| pw140321 [PATCH] r8125: add r8125 ethernet poll mode driver 0-day Robot
2024-05-27 7:44 ` |SUCCESS| pw140321 [PATCH] r8125: add r8125 ethernet poll mode drive dpdklab
2024-05-27 7:45 ` dpdklab
2024-05-27 7:46 ` dpdklab
2024-05-27 7:47 ` dpdklab
2024-05-27 7:48 ` dpdklab
2024-05-27 7:48 ` dpdklab
2024-05-27 7:49 ` dpdklab
2024-05-27 7:49 ` dpdklab
2024-05-27 7:49 ` dpdklab
2024-05-27 7:50 ` dpdklab
2024-05-27 7:50 ` dpdklab
2024-05-27 7:51 ` dpdklab
2024-05-27 7:51 ` dpdklab
2024-05-27 7:52 ` dpdklab
2024-05-27 7:53 ` dpdklab
2024-05-27 7:53 ` dpdklab
2024-05-27 7:54 ` dpdklab
2024-05-27 7:54 ` dpdklab
2024-05-27 7:55 ` dpdklab
2024-05-27 7:55 ` dpdklab
2024-05-27 7:56 ` dpdklab
2024-05-27 7:57 ` dpdklab
2024-05-27 7:57 ` dpdklab
2024-05-27 7:59 ` dpdklab
2024-05-27 8:08 ` dpdklab
2024-05-27 8:11 ` dpdklab
2024-05-27 8:13 ` dpdklab
2024-05-27 8:13 ` dpdklab
2024-05-27 8:14 ` dpdklab
2024-05-27 8:15 ` dpdklab
2024-05-27 8:15 ` dpdklab
2024-05-27 8:16 ` dpdklab
2024-05-27 8:16 ` dpdklab
2024-05-27 8:18 ` dpdklab
2024-05-27 8:19 ` dpdklab
2024-05-27 8:27 ` dpdklab
2024-05-27 8:28 ` dpdklab
2024-05-27 8:29 ` dpdklab
2024-05-27 8:29 ` dpdklab
2024-05-27 8:30 ` dpdklab
2024-05-27 8:30 ` dpdklab
2024-05-27 8:31 ` dpdklab
2024-05-27 8:31 ` dpdklab
2024-05-27 8:32 ` dpdklab
2024-05-27 8:32 ` dpdklab
2024-05-27 8:33 ` dpdklab
2024-05-27 8:33 ` dpdklab
2024-05-27 8:34 ` dpdklab
2024-05-27 8:34 ` dpdklab
2024-05-27 8:34 ` dpdklab
2024-05-27 8:35 ` dpdklab
2024-05-27 8:35 ` dpdklab
2024-05-27 8:35 ` dpdklab
2024-05-27 8:36 ` dpdklab
2024-05-27 8:36 ` dpdklab
2024-05-27 8:36 ` dpdklab
2024-05-27 8:37 ` dpdklab
2024-05-27 8:37 ` dpdklab
2024-05-27 8:37 ` dpdklab
2024-05-27 8:38 ` dpdklab
2024-05-27 8:40 ` dpdklab
2024-05-27 8:41 ` dpdklab
2024-05-27 8:42 ` dpdklab
2024-05-27 8:42 ` dpdklab
2024-05-27 8:42 ` dpdklab
2024-05-27 8:43 ` dpdklab
2024-05-27 8:43 ` dpdklab
2024-05-27 8:43 ` dpdklab
2024-05-27 8:43 ` dpdklab
2024-05-27 8:44 ` dpdklab
2024-05-27 8:44 ` dpdklab
2024-05-27 8:44 ` dpdklab
2024-05-27 8:45 ` dpdklab
2024-05-27 8:45 ` dpdklab
2024-05-27 9:12 ` dpdklab
2024-05-27 9:15 ` dpdklab
2024-05-27 9:16 ` dpdklab
2024-05-29 11:49 ` dpdklab
2024-05-29 12:25 ` 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=202405270627.44R6RflF2779111@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).