From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143949 [PATCH] doc: fix crashes in scheduler_multicore due to incorrect variable usage
Date: Wed, 11 Sep 2024 23:37:07 +0800 [thread overview]
Message-ID: <202409111537.48BFb7nN342430@localhost.localdomain> (raw)
In-Reply-To: <tencent_D05F50029A27CC0278BE8862B42491F7410A@qq.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143949
_Compilation OK_
Submitter: Yong Liang <1269690261@qq.com>
Date: Wed, 11 Sep 2024 23:56:45 +0800
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: b3485f4293997d35b6daecc3437bb0c183a51fb3
143949 --> 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-09-11 16:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_D05F50029A27CC0278BE8862B42491F7410A@qq.com>
2024-09-11 15:37 ` qemudev [this message]
2024-09-11 15:41 ` qemudev
2024-09-11 15:57 ` checkpatch
2024-09-11 16:44 ` 0-day Robot
2024-09-11 23:12 ` |SUCCESS| pw143949 [PATCH] doc: fix crashes in scheduler_multicore d dpdklab
2024-09-11 23:17 ` dpdklab
2024-09-12 1:10 ` dpdklab
2024-09-12 3:13 ` dpdklab
2024-09-12 5:40 ` |PENDING| " dpdklab
2024-09-12 5:51 ` dpdklab
2024-09-12 6:09 ` dpdklab
2024-09-12 6:11 ` dpdklab
2024-09-12 6:23 ` |SUCCESS| " dpdklab
2024-09-12 6:42 ` dpdklab
2024-09-12 6:43 ` dpdklab
2024-09-12 7:21 ` dpdklab
2024-09-12 7:27 ` dpdklab
2024-09-12 7:37 ` dpdklab
2024-09-12 8:13 ` dpdklab
2024-09-12 8:29 ` dpdklab
2024-09-12 8:43 ` dpdklab
2024-09-12 8:49 ` dpdklab
2024-09-12 8:56 ` dpdklab
2024-09-12 18:48 ` dpdklab
2024-09-15 11:28 ` dpdklab
2024-09-15 16:03 ` 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=202409111537.48BFb7nN342430@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).