From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw149646-149660 [PATCH v5 15/15] net/xsc: add ethdev link and MTU ops
Date: Tue, 7 Jan 2025 10:29:52 +0800 [thread overview]
Message-ID: <202501070229.5072Tqdv2840981@localhost.localdomain> (raw)
In-Reply-To: <20250107025015.1962467-16-wanry@yunsilicon.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/149660
_Compilation OK_
Submitter: WanRenyong <wanry@yunsilicon.com>
Date: Tue, 07 Jan 2025 10:49:40 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 94ad302b4ebba4a5b6706a1c43ea0505e5098169
149646-149660 --> 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-01-07 3:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250107025015.1962467-16-wanry@yunsilicon.com>
2025-01-07 2:29 ` qemudev [this message]
2025-01-07 2:34 ` qemudev
2025-01-07 2:52 ` |SUCCESS| pw149660 " checkpatch
2025-01-07 3:44 ` 0-day Robot
2025-01-07 7:51 ` |SUCCESS| pw149646-149660 [PATCH] [v5,15/15] net/xsc: add ethdev lin dpdklab
2025-01-07 7:53 ` dpdklab
2025-01-07 7:58 ` dpdklab
2025-01-07 8:10 ` dpdklab
2025-01-07 8:16 ` dpdklab
2025-01-07 8:27 ` dpdklab
2025-01-07 8:56 ` dpdklab
2025-01-07 9:09 ` dpdklab
2025-01-07 9:16 ` dpdklab
2025-01-07 9:33 ` dpdklab
2025-01-07 9:52 ` dpdklab
2025-01-07 14:58 ` |PENDING| " dpdklab
2025-01-08 1:33 ` |SUCCESS| " dpdklab
2025-01-08 1:39 ` dpdklab
2025-01-08 1:52 ` dpdklab
2025-01-08 1:55 ` dpdklab
2025-01-08 2:00 ` dpdklab
2025-01-08 2:04 ` dpdklab
2025-01-08 2:09 ` dpdklab
2025-01-08 2:09 ` dpdklab
2025-01-08 2:16 ` dpdklab
2025-01-08 2:49 ` |PENDING| " dpdklab
2025-01-08 3:45 ` |SUCCESS| " dpdklab
2025-01-08 3: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=202501070229.5072Tqdv2840981@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).