From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw157884-157903 [PATCH v2 21/21] net/ntnic: fix potential name conflict
Date: Tue, 21 Oct 2025 00:13:17 +0800 [thread overview]
Message-ID: <202510201613.59KGDHAp2803867@localhost.localdomain> (raw)
In-Reply-To: <20251020164336.283664-22-sil-plv@napatech.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/157903
_Compilation OK_
Submitter: Serhii Iliushyk <sil-plv@napatech.com>
Date: Mon, 20 Oct 2025 18:43:10 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: dce56012d806099005d3cf28a11a6cba140c0f31
157884-157903 --> 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-10-20 16:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251020164336.283664-22-sil-plv@napatech.com>
2025-10-20 16:13 ` qemudev [this message]
2025-10-20 16:18 ` qemudev
2025-10-20 16:47 ` |SUCCESS| pw157903 " checkpatch
2025-10-20 17:12 ` |SUCCESS| pw157884-157903 [PATCH] [v2,21/21] net/ntnic: fix potentia dpdklab
2025-10-20 17:12 ` |PENDING| " dpdklab
2025-10-20 17:14 ` |SUCCESS| " dpdklab
2025-10-20 17:23 ` |PENDING| " dpdklab
2025-10-20 17:32 ` |SUCCESS| " dpdklab
2025-10-20 17:33 ` dpdklab
2025-10-20 17:35 ` dpdklab
2025-10-20 17:36 ` dpdklab
2025-10-20 17:36 ` |PENDING| " dpdklab
2025-10-20 17:39 ` |SUCCESS| " dpdklab
2025-10-20 17:39 ` dpdklab
2025-10-20 18:03 ` dpdklab
2025-10-20 18:04 ` dpdklab
2025-10-20 18:05 ` dpdklab
2025-10-20 18:17 ` dpdklab
2025-10-20 18:26 ` dpdklab
2025-10-20 21:01 ` |WARNING| " dpdklab
2025-10-20 21:30 ` |PENDING| " dpdklab
2025-10-20 21:36 ` |WARNING| " 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=202510201613.59KGDHAp2803867@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).