From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147880 [PATCH v2] eal/unix: optimize thread creation with glibc
Date: Sat, 2 Nov 2024 19:01:07 +0800 [thread overview]
Message-ID: <202411021101.4A2B17vO2787526@localhost.localdomain> (raw)
In-Reply-To: <20241102113232.2333703-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147880
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Sat, 2 Nov 2024 12:32:32 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: c79900e31e3e5a16c7f5410d0800315a0491ccad
147880 --> 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-11-02 11:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241102113232.2333703-1-david.marchand@redhat.com>
2024-11-02 11:01 ` qemudev [this message]
2024-11-02 11:05 ` qemudev
2024-11-02 11:32 ` |WARNING| " checkpatch
2024-11-02 12:07 ` |PENDING| pw147880 [PATCH] [v2] eal/unix: optimize thread creation w dpdklab
2024-11-02 12:13 ` dpdklab
2024-11-02 12:19 ` |SUCCESS| " dpdklab
2024-11-02 12:20 ` dpdklab
2024-11-02 12:24 ` |SUCCESS| pw147880 [PATCH v2] eal/unix: optimize thread creation with glibc 0-day Robot
2024-11-02 12:28 ` |SUCCESS| pw147880 [PATCH] [v2] eal/unix: optimize thread creation w dpdklab
2024-11-02 12:28 ` dpdklab
2024-11-02 12:29 ` dpdklab
2024-11-02 12:31 ` dpdklab
2024-11-02 12:33 ` dpdklab
2024-11-02 12:35 ` dpdklab
2024-11-02 12:45 ` dpdklab
2024-11-02 12:45 ` dpdklab
2024-11-02 13:01 ` dpdklab
2024-11-02 15:27 ` 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=202411021101.4A2B17vO2787526@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).