From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137988 [PATCH v4] net/ice: add diagnostic support in Tx path
Date: Tue, 5 Mar 2024 18:38:25 +0800 [thread overview]
Message-ID: <202403051038.425AcPHu1899760@localhost.localdomain> (raw)
In-Reply-To: <20240305101843.769539-1-mingjinx.ye@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137988
_Compilation OK_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Tue, 5 Mar 2024 10:18:42 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 6cd9fa5ad4bba96acc5e451715c6616a7af672c3
137988 --> 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 prev parent reply other threads:[~2024-03-05 11:03 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240305101843.769539-1-mingjinx.ye@intel.com>
2024-03-05 10:37 ` checkpatch
2024-03-05 10:38 ` qemudev [this message]
2024-03-05 10:42 ` qemudev
2024-03-05 11:26 ` 0-day Robot
2024-03-05 14:00 ` |SUCCESS| pw137988 [PATCH] [v4] net/ice: add diagnostic support in T dpdklab
2024-03-05 14:08 ` dpdklab
2024-03-05 14:46 ` dpdklab
2024-03-05 14:48 ` dpdklab
2024-03-05 14:49 ` dpdklab
2024-03-05 14:49 ` dpdklab
2024-03-05 14:51 ` dpdklab
2024-03-05 14:51 ` dpdklab
2024-03-05 14:52 ` dpdklab
2024-03-05 14:55 ` dpdklab
2024-03-05 14:55 ` dpdklab
2024-03-05 14:57 ` dpdklab
2024-03-05 14:57 ` dpdklab
2024-03-05 14:58 ` dpdklab
2024-03-05 14:59 ` dpdklab
2024-03-05 15:05 ` dpdklab
2024-03-05 15:05 ` dpdklab
2024-03-05 15:10 ` dpdklab
2024-03-05 15:14 ` dpdklab
2024-03-05 15:21 ` dpdklab
2024-03-05 16:22 ` dpdklab
2024-03-05 16:22 ` dpdklab
2024-03-05 16:23 ` dpdklab
2024-03-05 16:29 ` dpdklab
2024-03-05 16:30 ` dpdklab
2024-03-05 16:30 ` dpdklab
2024-03-05 16:31 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:33 ` dpdklab
2024-03-05 16:33 ` dpdklab
2024-03-05 16:33 ` dpdklab
2024-03-05 16:33 ` dpdklab
2024-03-05 16:33 ` dpdklab
2024-03-05 16:36 ` dpdklab
2024-03-05 16:39 ` dpdklab
2024-03-05 16:40 ` dpdklab
2024-03-05 16:40 ` dpdklab
2024-03-05 16:40 ` dpdklab
2024-03-05 16:41 ` dpdklab
2024-03-05 16:41 ` dpdklab
2024-03-05 16:41 ` dpdklab
2024-03-05 16:49 ` dpdklab
2024-03-05 16:50 ` dpdklab
2024-03-05 16:50 ` dpdklab
2024-03-05 18:01 ` dpdklab
2024-03-05 19:21 ` dpdklab
2024-03-09 11:02 ` dpdklab
2024-03-09 11:35 ` dpdklab
2024-03-09 12:07 ` 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=202403051038.425AcPHu1899760@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).