From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw152916 [PATCH] net/e1000: fix eeprom dump failure
Date: Tue, 15 Apr 2025 15:15:16 +0800 [thread overview]
Message-ID: <202504150715.53F7FGPc3244999@localhost.localdomain> (raw)
In-Reply-To: <20250415074802.454733-1-yuanx.wang@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/152916
_Compilation OK_
Submitter: Yuan Wang <yuanx.wang@intel.com>
Date: Tue, 15 Apr 2025 15:48:02 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: d7817c378fecd07c59360667f93c25dff4b1a145
152916 --> 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:[~2025-04-15 7:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250415074802.454733-1-yuanx.wang@intel.com>
2025-04-15 7:15 ` qemudev [this message]
2025-04-15 7:19 ` qemudev
2025-04-15 7:49 ` checkpatch
2025-04-15 8:43 ` 0-day Robot
2025-04-15 8:50 ` dpdklab
2025-04-15 8:55 ` |PENDING| " dpdklab
2025-04-15 9:01 ` |SUCCESS| " dpdklab
2025-04-15 9:02 ` dpdklab
2025-04-15 9:02 ` dpdklab
2025-04-15 9:05 ` dpdklab
2025-04-15 9:10 ` dpdklab
2025-04-15 9:21 ` dpdklab
2025-04-15 9:24 ` |PENDING| " dpdklab
2025-04-15 9:31 ` dpdklab
2025-04-15 9:54 ` dpdklab
2025-04-15 10:07 ` |SUCCESS| " dpdklab
2025-04-15 10:08 ` dpdklab
2025-04-15 10:09 ` |PENDING| " dpdklab
2025-04-15 10:37 ` |SUCCESS| " dpdklab
2025-04-15 10:46 ` dpdklab
2025-04-15 11:04 ` dpdklab
2025-04-15 11:24 ` dpdklab
2025-04-15 11:38 ` dpdklab
2025-04-15 13:12 ` dpdklab
2025-04-16 0:11 ` dpdklab
2025-04-16 0:46 ` 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=202504150715.53F7FGPc3244999@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).