From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140856 [PATCH v3] event/dsw: support explicit release only mode
Date: Fri, 7 Jun 2024 21:25:07 +0800 [thread overview]
Message-ID: <202406071325.457DP7Zs2253616@localhost.localdomain> (raw)
In-Reply-To: <20240607133615.374993-1-mattias.ronnblom@ericsson.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140856
_Compilation OK_
Submitter: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Date: Fri, 7 Jun 2024 15:36:15 +0200
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: 44e44c34c4e2e6ed5eff12424a1ebee21c13abcb
140856 --> 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-06-07 13:53 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240607133615.374993-1-mattias.ronnblom@ericsson.com>
2024-06-07 13:25 ` qemudev [this message]
2024-06-07 13:29 ` qemudev
2024-06-07 13:47 ` checkpatch
2024-06-07 15:05 ` 0-day Robot
2024-06-07 17:42 ` |SUCCESS| pw140856 [PATCH] [v3] event/dsw: support explicit release dpdklab
2024-06-07 17:44 ` dpdklab
2024-06-07 17:48 ` dpdklab
2024-06-07 17:49 ` dpdklab
2024-06-07 17:52 ` dpdklab
2024-06-07 17:54 ` dpdklab
2024-06-07 18:14 ` dpdklab
2024-06-07 18:15 ` dpdklab
2024-06-07 18:19 ` dpdklab
2024-06-07 18:22 ` dpdklab
2024-06-07 18:30 ` dpdklab
2024-06-07 18:31 ` dpdklab
2024-06-07 18:31 ` dpdklab
2024-06-07 18:32 ` dpdklab
2024-06-07 18:32 ` dpdklab
2024-06-07 18:32 ` dpdklab
2024-06-07 18:32 ` dpdklab
2024-06-07 18:45 ` dpdklab
2024-06-07 18:48 ` dpdklab
2024-06-07 18:49 ` dpdklab
2024-06-07 18:50 ` dpdklab
2024-06-07 18:53 ` dpdklab
2024-06-07 18:54 ` dpdklab
2024-06-07 18:55 ` dpdklab
2024-06-07 19:15 ` dpdklab
2024-06-07 19:49 ` dpdklab
2024-06-07 20:17 ` dpdklab
2024-06-07 20:18 ` dpdklab
2024-06-07 20:18 ` dpdklab
2024-06-07 20:18 ` dpdklab
2024-06-07 20:18 ` dpdklab
2024-06-07 20:18 ` dpdklab
2024-06-07 20:18 ` dpdklab
2024-06-07 20:18 ` dpdklab
2024-06-07 20:31 ` |FAILURE| " dpdklab
2024-06-07 20:37 ` |SUCCESS| " dpdklab
2024-06-07 20:38 ` |FAILURE| " dpdklab
2024-06-07 20:38 ` dpdklab
2024-06-07 20:39 ` dpdklab
2024-06-07 20:40 ` |SUCCESS| " dpdklab
2024-06-07 20:41 ` |FAILURE| " dpdklab
2024-06-07 20:42 ` |SUCCESS| " dpdklab
2024-06-07 20:43 ` dpdklab
2024-06-07 20:44 ` |FAILURE| " dpdklab
2024-06-07 20:52 ` |SUCCESS| " dpdklab
2024-06-07 20:54 ` dpdklab
2024-06-07 20:56 ` |FAILURE| " dpdklab
2024-06-07 20:58 ` dpdklab
2024-06-07 20:59 ` |SUCCESS| " dpdklab
2024-06-07 20:59 ` |FAILURE| " dpdklab
2024-06-07 21:00 ` dpdklab
2024-06-07 21:01 ` |SUCCESS| " dpdklab
2024-06-07 21:01 ` dpdklab
2024-06-07 21:02 ` |FAILURE| " dpdklab
2024-06-07 21:02 ` dpdklab
2024-06-07 21:04 ` |SUCCESS| " dpdklab
2024-06-07 21:06 ` |FAILURE| " dpdklab
2024-06-07 21:06 ` |SUCCESS| " dpdklab
2024-06-07 21:08 ` dpdklab
2024-06-07 21:08 ` dpdklab
2024-06-07 21:09 ` dpdklab
2024-06-07 21:09 ` dpdklab
2024-06-07 21:10 ` dpdklab
2024-06-07 21:10 ` dpdklab
2024-06-07 21:10 ` dpdklab
2024-06-07 21:11 ` dpdklab
2024-06-07 21:11 ` dpdklab
2024-06-07 21:12 ` dpdklab
2024-06-07 21:12 ` dpdklab
2024-06-07 21:13 ` dpdklab
2024-06-07 21:13 ` dpdklab
2024-06-07 21:13 ` dpdklab
2024-06-07 21:13 ` dpdklab
2024-06-07 21:14 ` dpdklab
2024-06-07 21:15 ` dpdklab
2024-06-07 21:15 ` dpdklab
2024-06-07 21:15 ` dpdklab
2024-06-07 21:16 ` dpdklab
2024-06-07 21:20 ` dpdklab
2024-06-07 21:22 ` dpdklab
2024-06-07 21:23 ` dpdklab
2024-06-07 21:26 ` dpdklab
2024-06-07 21:40 ` |FAILURE| " dpdklab
2024-06-07 21:53 ` |SUCCESS| " dpdklab
2024-06-07 21:53 ` dpdklab
2024-06-07 21:53 ` |FAILURE| " dpdklab
2024-06-07 21:59 ` |SUCCESS| " 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=202406071325.457DP7Zs2253616@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).