From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140357-140381 [PATCH 25/25] net/cpfl: updating idpf vc queue switch in cpfl
Date: Tue, 28 May 2024 15:53:44 +0800 [thread overview]
Message-ID: <202405280753.44S7ri8Q3747897@localhost.localdomain> (raw)
In-Reply-To: <20240528073630.867131-6-soumyadeep.hore@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140381
_Compilation OK_
Submitter: Soumyadeep Hore <soumyadeep.hore@intel.com>
Date: Tue, 28 May 2024 07:28:31 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 77e63757d2a0106a0cc519f5a82e2d749d16475a
140357-140381 --> 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-05-28 8:22 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240528073630.867131-6-soumyadeep.hore@intel.com>
2024-05-28 7:53 ` qemudev [this message]
2024-05-28 7:58 ` qemudev
2024-05-28 8:20 ` |WARNING| pw140381 " checkpatch
2024-05-28 9:23 ` |FAILURE| " 0-day Robot
2024-05-28 10:00 ` |SUCCESS| pw140357-140381 [PATCH] [25/25] net/cpfl: updating idpf vc dpdklab
2024-05-28 10:00 ` dpdklab
2024-05-28 10:41 ` dpdklab
2024-05-28 10:42 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-28 10:49 ` dpdklab
2024-05-28 10:49 ` dpdklab
2024-05-28 10:50 ` dpdklab
2024-05-28 10:50 ` dpdklab
2024-05-28 10:54 ` dpdklab
2024-05-28 10:56 ` dpdklab
2024-05-28 10:57 ` dpdklab
2024-05-28 10:58 ` dpdklab
2024-05-28 10:59 ` dpdklab
2024-05-28 10:59 ` dpdklab
2024-05-28 11:00 ` dpdklab
2024-05-28 11:00 ` dpdklab
2024-05-28 11:02 ` dpdklab
2024-05-28 11:02 ` dpdklab
2024-05-28 11:15 ` dpdklab
2024-05-28 11:36 ` dpdklab
2024-05-28 12:00 ` |FAILURE| " dpdklab
2024-05-28 12:01 ` dpdklab
2024-05-28 12:01 ` dpdklab
2024-05-28 12:07 ` dpdklab
2024-05-28 12:24 ` dpdklab
2024-05-28 12:32 ` |SUCCESS| " dpdklab
2024-05-28 12:32 ` dpdklab
2024-05-28 12:33 ` dpdklab
2024-05-28 12:35 ` dpdklab
2024-05-28 12:36 ` |FAILURE| " dpdklab
2024-05-28 12:37 ` dpdklab
2024-05-28 12:42 ` dpdklab
2024-05-28 12:42 ` dpdklab
2024-05-28 12:44 ` dpdklab
2024-05-28 12:45 ` |SUCCESS| " dpdklab
2024-05-28 12:45 ` dpdklab
2024-05-28 12:46 ` dpdklab
2024-05-28 12:46 ` |FAILURE| " dpdklab
2024-05-28 12:47 ` |SUCCESS| " dpdklab
2024-05-28 12:48 ` dpdklab
2024-05-28 12:49 ` |FAILURE| " dpdklab
2024-05-28 12:49 ` dpdklab
2024-05-28 12:50 ` dpdklab
2024-05-28 12:50 ` dpdklab
2024-05-28 12:51 ` |SUCCESS| " dpdklab
2024-05-28 12:52 ` dpdklab
2024-05-28 12:53 ` dpdklab
2024-05-28 12:54 ` dpdklab
2024-05-28 12:55 ` |FAILURE| " dpdklab
2024-05-28 12:55 ` dpdklab
2024-05-28 12:55 ` |SUCCESS| " dpdklab
2024-05-28 12:56 ` dpdklab
2024-05-28 12:56 ` |FAILURE| " dpdklab
2024-05-28 12:57 ` dpdklab
2024-05-28 12:57 ` |SUCCESS| " dpdklab
2024-05-28 12:57 ` |FAILURE| " dpdklab
2024-05-28 12:58 ` dpdklab
2024-05-28 12:58 ` dpdklab
2024-05-28 12:59 ` |SUCCESS| " dpdklab
2024-05-28 12:59 ` |FAILURE| " dpdklab
2024-05-28 13:00 ` dpdklab
2024-05-28 13:00 ` |SUCCESS| " dpdklab
2024-05-28 13:01 ` dpdklab
2024-05-28 13:02 ` |FAILURE| " dpdklab
2024-05-28 13:02 ` dpdklab
2024-05-28 13:03 ` dpdklab
2024-05-28 13:05 ` |SUCCESS| " dpdklab
2024-05-28 13:06 ` |FAILURE| " dpdklab
2024-05-28 13:07 ` dpdklab
2024-05-28 13:09 ` dpdklab
2024-05-28 13:10 ` |SUCCESS| " dpdklab
2024-05-28 13:19 ` dpdklab
2024-05-28 13:20 ` dpdklab
2024-05-28 13:20 ` |FAILURE| " dpdklab
2024-05-28 13:23 ` |SUCCESS| " dpdklab
2024-05-28 13:25 ` dpdklab
2024-05-28 14:17 ` dpdklab
2024-05-28 14:19 ` |FAILURE| " dpdklab
2024-05-28 14:46 ` |SUCCESS| " dpdklab
2024-05-30 2:21 ` dpdklab
2024-05-30 2:21 ` dpdklab
2024-05-30 2:24 ` 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=202405280753.44S7ri8Q3747897@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).