From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbarray_init()
Date: Thu, 14 Nov 2024 16:05:11 +0800 [thread overview]
Message-ID: <202411140805.4AE85BEB4017864@localhost.localdomain> (raw)
In-Reply-To: <tencent_B09D0FCCA142E4AE5ABFE584E92DCED8CB0A@qq.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148475
_Compilation OK_
Submitter: Congjie Zhou <zcjie0802@qq.com>
Date: Thu, 14 Nov 2024 16:37:10 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 78383e9816a8efe2ba16ec2ce65d51b94e6114e7
148475 --> 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-14 8:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_B09D0FCCA142E4AE5ABFE584E92DCED8CB0A@qq.com>
2024-11-14 8:05 ` qemudev [this message]
2024-11-14 8:09 ` qemudev
2024-11-14 8:39 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbarray_init checkpatch
2024-11-14 11:05 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbarray_init() 0-day Robot
2024-11-14 14:40 ` |SUCCESS| pw148475 [PATCH] eal/linux: redefine the name for rte_fbar dpdklab
2024-11-14 14:42 ` dpdklab
2024-11-14 14:50 ` dpdklab
2024-11-14 15:26 ` dpdklab
2024-11-14 16:00 ` dpdklab
2024-11-14 17:08 ` dpdklab
2024-11-14 17:15 ` dpdklab
2024-11-14 20:17 ` dpdklab
2024-11-14 21:00 ` dpdklab
2024-11-14 21:09 ` dpdklab
2024-11-14 21:42 ` |PENDING| " dpdklab
2024-11-14 22:53 ` dpdklab
2024-11-14 23:25 ` |WARNING| " dpdklab
2024-11-15 0:54 ` |SUCCESS| " 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=202411140805.4AE85BEB4017864@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).