From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148474 [PATCH] eal/linux: redefine the name for rte_fbarray_init()
Date: Thu, 14 Nov 2024 15:39:08 +0800 [thread overview]
Message-ID: <202411140739.4AE7d8X83957524@localhost.localdomain> (raw)
In-Reply-To: <tencent_B2075C50A573ADACC57248F416668EE42C09@qq.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148474
_Compilation OK_
Submitter: Congjie Zhou <zcjie0802@qq.com>
Date: Thu, 14 Nov 2024 16:10:39 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 78383e9816a8efe2ba16ec2ce65d51b94e6114e7
148474 --> 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:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_B2075C50A573ADACC57248F416668EE42C09@qq.com>
2024-11-14 7:39 ` qemudev [this message]
2024-11-14 7:43 ` qemudev
2024-11-14 8:12 ` |WARNING| pw148474 [PATCH] eal/linux: redefine the name for rte_fbarray_init checkpatch
2024-11-14 10:23 ` |SUCCESS| pw148474 [PATCH] eal/linux: redefine the name for rte_fbar dpdklab
2024-11-14 10:50 ` dpdklab
2024-11-14 10:50 ` dpdklab
2024-11-14 11:05 ` dpdklab
2024-11-14 11:40 ` dpdklab
2024-11-14 12:14 ` dpdklab
2024-11-14 15:47 ` dpdklab
2024-11-14 15:51 ` |PENDING| " dpdklab
2024-11-14 16:46 ` dpdklab
2024-11-14 16:56 ` |SUCCESS| " dpdklab
2024-11-14 17:24 ` |PENDING| " dpdklab
2024-11-14 17:41 ` |SUCCESS| " dpdklab
2024-11-14 18:21 ` |WARNING| " dpdklab
2024-11-14 19:58 ` |SUCCESS| " dpdklab
2024-11-14 20:31 ` dpdklab
2024-11-14 20:48 ` |WARNING| " dpdklab
2024-11-14 22:11 ` |SUCCESS| " dpdklab
2024-11-14 22:20 ` dpdklab
2024-11-14 22:39 ` 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=202411140739.4AE7d8X83957524@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).