From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125173-125174 [PATCH v5 2/2] eal: fix failure path race setting new thread affinity
Date: Thu, 16 Mar 2023 08:00:53 +0800 [thread overview]
Message-ID: <202303160000.32G00rwJ3906461@localhost.localdomain> (raw)
In-Reply-To: <1678925224-2706-3-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125174
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed, 15 Mar 2023 17:07:03 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 8c9bfcb1553d756eb5392a56ac7813b3865c3ec7
125173-125174 --> 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:[~2023-03-16 0:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1678925224-2706-3-git-send-email-roretzla@linux.microsoft.com>
2023-03-16 0:00 ` qemudev [this message]
2023-03-16 0:04 ` qemudev
2023-03-16 0:08 ` |SUCCESS| pw125174 " checkpatch
2023-03-16 2:19 ` 0-day Robot
2023-03-18 4:32 |SUCCESS| pw125173-125174 [PATCH] [v5, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-16 2:14 dpdklab
2023-03-16 2:13 dpdklab
2023-03-16 1:58 dpdklab
2023-03-16 0:58 dpdklab
2023-03-16 0:57 dpdklab
2023-03-16 0:49 dpdklab
2023-03-16 0:45 dpdklab
2023-03-16 0:44 dpdklab
2023-03-16 0:43 dpdklab
2023-03-16 0:42 dpdklab
2023-03-16 0:39 dpdklab
2023-03-16 0:37 dpdklab
2023-03-16 0:36 dpdklab
2023-03-16 0:33 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=202303160000.32G00rwJ3906461@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).