From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147864-147872 [PATCH v9 9/9] net/zxdh: add zxdh dev configure ops
Date: Fri, 1 Nov 2024 13:56:22 +0800 [thread overview]
Message-ID: <202411010556.4A15uMQA2489133@localhost.localdomain> (raw)
In-Reply-To: <20241101062156.2637339-10-wang.junlong1@zte.com.cn>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147872
_Compilation OK_
Submitter: Junlong Wang <wang.junlong1@zte.com.cn>
Date: Fri, 1 Nov 2024 14:21:47 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 171360df9f89a17f8b4177f01f11fa4473c74099
147864-147872 --> 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-11-01 6:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241101062156.2637339-10-wang.junlong1@zte.com.cn>
2024-11-01 5:56 ` qemudev [this message]
2024-11-01 6:00 ` qemudev
2024-11-01 6:29 ` |SUCCESS| pw147872 " checkpatch
2024-11-01 7:25 ` 0-day Robot
2024-11-01 9:17 ` |SUCCESS| pw147864-147872 [PATCH] [v9,9/9] net/zxdh: add zxdh dev co dpdklab
2024-11-01 10:14 ` dpdklab
2024-11-01 10:34 ` dpdklab
2024-11-01 10:41 ` dpdklab
2024-11-01 11:21 ` dpdklab
2024-11-01 12:54 ` |PENDING| " dpdklab
2024-11-01 13:55 ` dpdklab
2024-11-01 14:31 ` |SUCCESS| " dpdklab
2024-11-01 14:40 ` |PENDING| " dpdklab
2024-11-01 14:50 ` |SUCCESS| " dpdklab
2024-11-01 15:34 ` dpdklab
2024-11-01 20:14 ` dpdklab
2024-11-02 0:40 ` dpdklab
2024-11-02 14:23 ` dpdklab
2024-11-02 15:04 ` dpdklab
2024-11-02 16:45 ` dpdklab
2024-11-02 20:47 ` dpdklab
2024-11-03 1:56 ` dpdklab
2024-11-03 1:58 ` dpdklab
2024-11-06 4:22 ` 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=202411010556.4A15uMQA2489133@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).