From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142126-142127 [PATCH v2 2/2] net/cpfl: fix +ve error codes for received ctlq messages
Date: Fri, 5 Jul 2024 20:27:47 +0800 [thread overview]
Message-ID: <202407051227.465CRleV1211654@localhost.localdomain> (raw)
In-Reply-To: <20240705050831.2639342-3-soumyadeep.hore@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/142127
_Compilation OK_
Submitter: Soumyadeep Hore <soumyadeep.hore@intel.com>
Date: Fri, 5 Jul 2024 05:08:30 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 5287405d9f8fed3ec20dae1584d76b5cdbf3af0f
142126-142127 --> 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-07-05 12:56 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240705050831.2639342-3-soumyadeep.hore@intel.com>
2024-07-05 5:57 ` |SUCCESS| pw142127 " checkpatch
2024-07-05 6:37 ` |SUCCESS| pw142126-142127 [PATCH] [v2,2/2] net/cpfl: fix +ve error c dpdklab
2024-07-05 6:41 ` dpdklab
2024-07-05 6:44 ` dpdklab
2024-07-05 6:49 ` |PENDING| " dpdklab
2024-07-05 6:53 ` dpdklab
2024-07-05 6:54 ` dpdklab
2024-07-05 6:54 ` dpdklab
2024-07-05 6:54 ` |SUCCESS| " dpdklab
2024-07-05 6:54 ` |PENDING| " dpdklab
2024-07-05 6:59 ` |SUCCESS| " dpdklab
2024-07-05 7:00 ` |PENDING| " dpdklab
2024-07-05 7:01 ` dpdklab
2024-07-05 7:01 ` |SUCCESS| " dpdklab
2024-07-05 7:02 ` |PENDING| " dpdklab
2024-07-05 7:04 ` dpdklab
2024-07-05 7:07 ` dpdklab
2024-07-05 7:07 ` |SUCCESS| " dpdklab
2024-07-05 7:08 ` |PENDING| " dpdklab
2024-07-05 7:08 ` |SUCCESS| " dpdklab
2024-07-05 7:10 ` |PENDING| " dpdklab
2024-07-05 7:11 ` dpdklab
2024-07-05 7:14 ` dpdklab
2024-07-05 7:15 ` dpdklab
2024-07-05 7:19 ` dpdklab
2024-07-05 7:20 ` dpdklab
2024-07-05 7:26 ` dpdklab
2024-07-05 7:27 ` |SUCCESS| " dpdklab
2024-07-05 7:27 ` |PENDING| " dpdklab
2024-07-05 7:41 ` dpdklab
2024-07-05 7:43 ` |SUCCESS| pw142127 [PATCH v2 2/2] net/cpfl: fix +ve error codes for received ctlq messages 0-day Robot
2024-07-05 7:47 ` |SUCCESS| pw142126-142127 [PATCH] [v2,2/2] net/cpfl: fix +ve error c dpdklab
2024-07-05 8:02 ` |PENDING| " dpdklab
2024-07-05 8:03 ` |SUCCESS| " dpdklab
2024-07-05 12:27 ` qemudev [this message]
2024-07-05 12:32 ` |SUCCESS| pw142126-142127 [PATCH v2 2/2] net/cpfl: fix +ve error codes for received ctlq messages qemudev
2024-07-05 13:23 ` |SUCCESS| pw142126-142127 [PATCH] [v2,2/2] net/cpfl: fix +ve error c dpdklab
2024-07-05 13:28 ` dpdklab
2024-07-05 13:33 ` dpdklab
2024-07-05 13:53 ` dpdklab
2024-07-05 13:57 ` dpdklab
2024-07-05 18:02 ` |PENDING| " dpdklab
2024-07-05 18:03 ` dpdklab
2024-07-05 18:05 ` dpdklab
2024-07-05 18:07 ` dpdklab
2024-07-05 18:08 ` dpdklab
2024-07-05 18:09 ` dpdklab
2024-07-05 18:12 ` dpdklab
2024-07-05 18:13 ` dpdklab
2024-07-05 18:18 ` dpdklab
2024-07-05 18:24 ` dpdklab
2024-07-05 18:25 ` dpdklab
2024-07-05 18:25 ` dpdklab
2024-07-05 18:26 ` dpdklab
2024-07-05 18:27 ` dpdklab
2024-07-05 18:30 ` dpdklab
2024-07-05 18:30 ` dpdklab
2024-07-05 18:30 ` dpdklab
2024-07-05 18:31 ` dpdklab
2024-07-05 18:32 ` dpdklab
2024-07-05 18:33 ` dpdklab
2024-07-05 18:35 ` dpdklab
2024-07-05 18:38 ` dpdklab
2024-07-05 18:39 ` dpdklab
2024-07-05 18:41 ` dpdklab
2024-07-05 18:42 ` dpdklab
2024-07-05 18:43 ` dpdklab
2024-07-05 18:43 ` dpdklab
2024-07-05 18:43 ` dpdklab
2024-07-05 18:45 ` dpdklab
2024-07-05 18:48 ` dpdklab
2024-07-05 18:53 ` dpdklab
2024-07-05 18:53 ` dpdklab
2024-07-05 18:58 ` dpdklab
2024-07-05 18:58 ` dpdklab
2024-07-05 19:05 ` |SUCCESS| " dpdklab
2024-07-05 19:11 ` |PENDING| " dpdklab
2024-07-05 20:51 ` |SUCCESS| " dpdklab
2024-07-06 1:18 ` |PENDING| " dpdklab
2024-07-06 1:21 ` dpdklab
2024-07-06 1:28 ` dpdklab
2024-07-06 1:30 ` dpdklab
2024-07-06 1:32 ` dpdklab
2024-07-06 1:39 ` dpdklab
2024-07-06 1:48 ` dpdklab
2024-07-06 1:49 ` dpdklab
2024-07-06 1:56 ` dpdklab
2024-07-06 1:58 ` dpdklab
2024-07-06 2:06 ` dpdklab
2024-07-06 2:09 ` dpdklab
2024-07-06 2:45 ` dpdklab
2024-07-06 2:54 ` dpdklab
2024-07-06 2:59 ` |SUCCESS| " dpdklab
2024-07-06 3:24 ` |PENDING| " dpdklab
2024-07-06 3:29 ` dpdklab
2024-07-06 3:33 ` dpdklab
2024-07-06 3:36 ` dpdklab
2024-07-06 3:40 ` dpdklab
2024-07-06 3:48 ` dpdklab
2024-07-06 4:08 ` dpdklab
2024-07-06 4:16 ` dpdklab
2024-07-06 4:25 ` dpdklab
2024-07-06 4:32 ` dpdklab
2024-07-06 4:33 ` dpdklab
2024-07-06 4:40 ` dpdklab
2024-07-06 4:41 ` dpdklab
2024-07-06 4:44 ` dpdklab
2024-07-06 4:46 ` dpdklab
2024-07-06 4:52 ` |SUCCESS| " dpdklab
2024-07-06 15:59 ` dpdklab
2024-07-06 16:52 ` dpdklab
2024-07-06 17:07 ` dpdklab
2024-07-08 20:11 ` dpdklab
2024-07-08 20: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=202407051227.465CRleV1211654@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).