From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw130873 [PATCH] eal: fix memory initialization deadlock
Date: Wed, 30 Aug 2023 18:26:10 +0800 [thread overview]
Message-ID: <202308301026.37UAQAEt598143@localhost.localdomain> (raw)
In-Reply-To: <20230830103303.2428995-1-artemyko@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/130873
_Compilation OK_
Submitter: Artemy Kovalyov <artemyko@nvidia.com>
Date: Wed, 30 Aug 2023 13:33:03 +0300
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: b7b8de26f34d39c8aaded44d8a468da5e68f19da
130873 --> 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-08-30 10:40 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230830103303.2428995-1-artemyko@nvidia.com>
2023-08-30 10:26 ` qemudev [this message]
2023-08-30 10:30 ` qemudev
2023-08-30 10:34 ` checkpatch
2023-08-30 11:39 ` 0-day Robot
2023-08-30 11:02 dpdklab
2023-08-30 11:03 dpdklab
2023-08-30 11:05 dpdklab
2023-08-30 11:06 dpdklab
2023-08-30 11:07 dpdklab
2023-08-30 11:07 dpdklab
2023-08-30 11:09 dpdklab
2023-08-30 11:10 dpdklab
2023-08-30 11:11 dpdklab
2023-08-30 11:13 dpdklab
2023-08-30 11:14 dpdklab
2023-08-30 11:18 dpdklab
2023-08-30 11:18 dpdklab
2023-08-30 11:19 dpdklab
2023-08-30 11:21 dpdklab
2023-08-30 11:22 dpdklab
2023-08-30 11:23 dpdklab
2023-08-30 11:25 dpdklab
2023-08-30 11:25 dpdklab
2023-08-30 11:25 dpdklab
2023-08-30 11:27 dpdklab
2023-08-30 11:36 dpdklab
2023-08-30 11:43 dpdklab
2023-08-30 11:43 dpdklab
2023-08-30 11:43 dpdklab
2023-08-30 11:45 dpdklab
2023-08-30 11:46 dpdklab
2023-08-30 11:48 dpdklab
2023-08-30 11:49 dpdklab
2023-08-30 11:51 dpdklab
2023-08-30 11:59 dpdklab
2023-08-30 12:01 dpdklab
2023-08-30 12:03 dpdklab
2023-08-30 12:04 dpdklab
2023-08-30 12:06 dpdklab
2023-08-30 12:07 dpdklab
2023-08-30 12:15 dpdklab
2023-08-30 12:16 dpdklab
2023-08-30 12:23 dpdklab
2023-08-30 12:42 dpdklab
2023-08-30 12:44 dpdklab
2023-08-30 12:47 dpdklab
2023-08-30 12:51 dpdklab
2023-08-30 12:58 dpdklab
2023-08-30 13:03 dpdklab
2023-08-30 13:20 dpdklab
2023-08-30 13:31 dpdklab
2023-08-30 13:35 dpdklab
2023-08-30 13:40 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=202308301026.37UAQAEt598143@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).