From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147769-147815 [PATCH v5 80/80] net/ntnic: add MTU configuration
Date: Thu, 31 Oct 2024 06:46:06 +0800 [thread overview]
Message-ID: <202410302246.49UMk6wa3407833@localhost.localdomain> (raw)
In-Reply-To: <20241030213940.3470062-81-sil-plv@napatech.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147815
_Compilation OK_
Submitter: Serhii Iliushyk <sil-plv@napatech.com>
Date: Wed, 30 Oct 2024 22:38:08 +0100
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 1bbd8938e387037baeccfcfa63a8420f0fa30899
147769-147815 --> 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-10-30 23:19 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241030213940.3470062-81-sil-plv@napatech.com>
2024-10-30 22:46 ` qemudev [this message]
2024-10-30 22:50 ` qemudev
2024-10-30 23:15 ` |SUCCESS| pw147815 " checkpatch
2024-10-31 0:05 ` |FAILURE| " 0-day Robot
2024-10-31 17:25 ` |SUCCESS| pw147769-147815 [PATCH] [v5,80/80] net/ntnic: add MTU conf dpdklab
2024-10-31 17:41 ` dpdklab
2024-10-31 18:17 ` |PENDING| " dpdklab
2024-10-31 18:33 ` dpdklab
2024-10-31 19:03 ` dpdklab
2024-10-31 19:15 ` |SUCCESS| " dpdklab
2024-10-31 19:15 ` |PENDING| " dpdklab
2024-10-31 19:21 ` dpdklab
2024-10-31 19:23 ` |SUCCESS| " dpdklab
2024-10-31 19:40 ` dpdklab
2024-10-31 19:54 ` dpdklab
2024-10-31 20:10 ` dpdklab
2024-10-31 20:23 ` dpdklab
2024-10-31 20:30 ` dpdklab
2024-10-31 20:37 ` dpdklab
2024-10-31 20:41 ` dpdklab
2024-10-31 21:14 ` dpdklab
2024-10-31 21:26 ` |PENDING| " dpdklab
2024-10-31 21:29 ` |SUCCESS| " dpdklab
2024-10-31 22:07 ` dpdklab
2024-11-01 2:35 ` dpdklab
2024-11-01 3:25 ` dpdklab
2024-11-01 4:10 ` dpdklab
2024-11-01 4:10 ` dpdklab
2024-11-01 5:11 ` dpdklab
2024-11-01 5:33 ` dpdklab
2024-11-01 10:11 ` dpdklab
2024-11-01 11:09 ` dpdklab
2024-11-01 12:20 ` dpdklab
2024-11-01 18:12 ` dpdklab
2024-11-01 18:47 ` dpdklab
2024-11-01 19:05 ` dpdklab
2024-11-01 19:40 ` dpdklab
2024-11-02 8:56 ` dpdklab
2024-11-02 9:37 ` dpdklab
2024-11-02 18:53 ` dpdklab
2024-11-02 19:07 ` dpdklab
2024-11-02 23:19 ` dpdklab
2024-11-02 23:21 ` dpdklab
2024-11-02 23:27 ` dpdklab
2024-11-02 23:29 ` dpdklab
2024-11-05 15:27 ` dpdklab
2024-11-05 16:43 ` 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=202410302246.49UMk6wa3407833@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).