From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147759 [PATCH] Revert "eal/unix: fix thread creation"
Date: Thu, 31 Oct 2024 02:39:07 +0800 [thread overview]
Message-ID: <202410301839.49UId7oR3130113@localhost.localdomain> (raw)
In-Reply-To: <20241030190945.409721-1-luca.boccassi@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147759
_Compilation OK_
Submitter: Luca Boccassi <luca.boccassi@gmail.com>
Date: Wed, 30 Oct 2024 19:08:41 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2a682d65f8dbe1e8be9cc2425095827e18c700e3
147759 --> 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 19:12 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241030190945.409721-1-luca.boccassi@gmail.com>
2024-10-30 18:39 ` qemudev [this message]
2024-10-30 18:43 ` qemudev
2024-10-30 19:11 ` |WARNING| " checkpatch
2024-10-30 20:04 ` |SUCCESS| " 0-day Robot
2024-10-31 0:45 ` dpdklab
2024-10-31 0:59 ` dpdklab
2024-10-31 2:57 ` dpdklab
2024-10-31 3:07 ` dpdklab
2024-10-31 3:26 ` dpdklab
2024-10-31 3:34 ` dpdklab
2024-10-31 3:58 ` dpdklab
2024-10-31 4:34 ` dpdklab
2024-10-31 4:35 ` |PENDING| " dpdklab
2024-10-31 5:13 ` |SUCCESS| " dpdklab
2024-10-31 8:55 ` |PENDING| " dpdklab
2024-10-31 9:09 ` |SUCCESS| " dpdklab
2024-10-31 9:30 ` |PENDING| " dpdklab
2024-10-31 9:30 ` dpdklab
2024-10-31 9:39 ` |SUCCESS| " dpdklab
2024-10-31 10:04 ` |PENDING| " dpdklab
2024-10-31 10:11 ` |SUCCESS| " dpdklab
2024-10-31 10:26 ` dpdklab
2024-10-31 10:38 ` dpdklab
2024-10-31 10:51 ` |PENDING| " dpdklab
2024-10-31 11:57 ` |SUCCESS| " dpdklab
2024-10-31 14:54 ` |PENDING| " dpdklab
2024-10-31 15:00 ` |SUCCESS| " dpdklab
2024-10-31 16:00 ` dpdklab
2024-10-31 16:58 ` dpdklab
2024-10-31 20:12 ` dpdklab
2024-10-31 22:28 ` dpdklab
2024-10-31 22:42 ` dpdklab
2024-10-31 22:47 ` dpdklab
2024-10-31 22:47 ` dpdklab
2024-10-31 23:00 ` dpdklab
2024-10-31 23:00 ` dpdklab
2024-10-31 23:03 ` dpdklab
2024-10-31 23:03 ` dpdklab
2024-11-01 0:55 ` dpdklab
2024-11-01 1:31 ` dpdklab
2024-11-01 1:50 ` dpdklab
2024-11-01 2:25 ` dpdklab
2024-11-01 5:19 ` dpdklab
2024-11-01 23:53 ` dpdklab
2024-11-02 0:13 ` dpdklab
2024-11-02 15:48 ` dpdklab
2024-11-02 17:29 ` dpdklab
2024-11-02 21:01 ` dpdklab
2024-11-02 21:03 ` dpdklab
2024-11-02 22:23 ` dpdklab
2024-11-02 22:24 ` dpdklab
2024-11-05 0:12 ` dpdklab
2024-11-05 0:39 ` 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=202410301839.49UId7oR3130113@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).