From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148106 [PATCH v2 1/1] baseband/acc: fix ring memory allocation logic
Date: Fri, 8 Nov 2024 08:01:08 +0800 [thread overview]
Message-ID: <202411080001.4A8018XC2961357@localhost.localdomain> (raw)
In-Reply-To: <20241108003238.1921588-2-nicolas.chautru@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148106
_Compilation OK_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Thu, 7 Nov 2024 16:32:38 -0800
DPDK git baseline: Repo:dpdk-next-baseband
Branch: for-main
CommitID: 340d000bc400ae4053723cf18c4ba822e8c5bec5
148106 --> 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-08 0:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241108003238.1921588-2-nicolas.chautru@intel.com>
2024-11-08 0:01 ` qemudev [this message]
2024-11-08 0:05 ` qemudev
2024-11-08 0:32 ` checkpatch
2024-11-08 1:14 ` |PENDING| pw148106 [PATCH] [v2,1/1] baseband/acc: fix ring memory al dpdklab
2024-11-08 1:17 ` dpdklab
2024-11-08 1:19 ` dpdklab
2024-11-08 1:20 ` |SUCCESS| " dpdklab
2024-11-08 1:21 ` |PENDING| " dpdklab
2024-11-08 1:27 ` dpdklab
2024-11-08 1:28 ` |SUCCESS| " dpdklab
2024-11-08 1:29 ` dpdklab
2024-11-08 1:32 ` dpdklab
2024-11-08 1:33 ` |SUCCESS| pw148106 [PATCH v2 1/1] baseband/acc: fix ring memory allocation logic 0-day Robot
2024-11-08 1:34 ` |SUCCESS| pw148106 [PATCH] [v2,1/1] baseband/acc: fix ring memory al dpdklab
2024-11-08 1:39 ` dpdklab
2024-11-08 1:53 ` dpdklab
2024-11-08 1:54 ` dpdklab
2024-11-08 2:01 ` dpdklab
2024-11-08 2:01 ` dpdklab
2024-11-08 2:19 ` dpdklab
2024-11-08 2:24 ` dpdklab
2024-11-08 3:18 ` dpdklab
2024-11-08 5:27 ` 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=202411080001.4A8018XC2961357@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).