From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140327-140333 [PATCH v4 7/7] dma/odm: add remaining ops
Date: Mon, 27 May 2024 22:51:14 +0800 [thread overview]
Message-ID: <202405271451.44REpEgZ3139228@localhost.localdomain> (raw)
In-Reply-To: <20240527151704.433098-8-anoobj@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140333
_Compilation OK_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Mon, 27 May 2024 15:16:45 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 77e63757d2a0106a0cc519f5a82e2d749d16475a
140327-140333 --> 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-05-27 15:19 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240527151704.433098-8-anoobj@marvell.com>
2024-05-27 14:51 ` qemudev [this message]
2024-05-27 14:55 ` qemudev
2024-05-27 15:19 ` |WARNING| pw140333 " checkpatch
2024-05-27 15:57 ` |SUCCESS| pw140327-140333 [PATCH] [v4,7/7] dma/odm: add remaining op dpdklab
2024-05-27 15:58 ` dpdklab
2024-05-27 15:58 ` dpdklab
2024-05-27 15:59 ` dpdklab
2024-05-27 15:59 ` dpdklab
2024-05-27 15:59 ` dpdklab
2024-05-27 15:59 ` dpdklab
2024-05-27 16:00 ` dpdklab
2024-05-27 16:00 ` dpdklab
2024-05-27 16:00 ` dpdklab
2024-05-27 16:01 ` dpdklab
2024-05-27 16:01 ` dpdklab
2024-05-27 16:01 ` dpdklab
2024-05-27 16:02 ` dpdklab
2024-05-27 16:02 ` dpdklab
2024-05-27 16:02 ` dpdklab
2024-05-27 16:02 ` dpdklab
2024-05-27 16:03 ` dpdklab
2024-05-27 16:03 ` dpdklab
2024-05-27 16:03 ` dpdklab
2024-05-27 16:04 ` dpdklab
2024-05-27 16:04 ` dpdklab
2024-05-27 16:05 ` dpdklab
2024-05-27 16:05 ` dpdklab
2024-05-27 16:05 ` dpdklab
2024-05-27 16:05 ` dpdklab
2024-05-27 16:05 ` dpdklab
2024-05-27 16:06 ` dpdklab
2024-05-27 16:06 ` dpdklab
2024-05-27 16:07 ` dpdklab
2024-05-27 16:07 ` dpdklab
2024-05-27 16:08 ` dpdklab
2024-05-27 16:08 ` dpdklab
2024-05-27 16:09 ` dpdklab
2024-05-27 16:09 ` dpdklab
2024-05-27 16:09 ` dpdklab
2024-05-27 16:10 ` dpdklab
2024-05-27 16:10 ` dpdklab
2024-05-27 16:10 ` dpdklab
2024-05-27 16:10 ` dpdklab
2024-05-27 16:10 ` dpdklab
2024-05-27 16:12 ` dpdklab
2024-05-27 16:13 ` dpdklab
2024-05-27 16:13 ` dpdklab
2024-05-27 16:13 ` dpdklab
2024-05-27 16:14 ` dpdklab
2024-05-27 16:14 ` dpdklab
2024-05-27 16:14 ` dpdklab
2024-05-27 16:15 ` dpdklab
2024-05-27 16:16 ` dpdklab
2024-05-27 16:16 ` dpdklab
2024-05-27 16:18 ` dpdklab
2024-05-27 16:19 ` dpdklab
2024-05-27 16:21 ` dpdklab
2024-05-27 16:21 ` dpdklab
2024-05-27 16:22 ` dpdklab
2024-05-27 16:22 ` dpdklab
2024-05-27 16:23 ` |SUCCESS| pw140333 [PATCH v4 7/7] dma/odm: add remaining ops 0-day Robot
2024-05-27 16:23 ` |SUCCESS| pw140327-140333 [PATCH] [v4,7/7] dma/odm: add remaining op dpdklab
2024-05-27 16:23 ` dpdklab
2024-05-27 16:25 ` dpdklab
2024-05-27 16:25 ` dpdklab
2024-05-27 16:25 ` dpdklab
2024-05-27 16:26 ` dpdklab
2024-05-27 16:26 ` dpdklab
2024-05-27 16:26 ` dpdklab
2024-05-27 16:27 ` dpdklab
2024-05-27 16:27 ` dpdklab
2024-05-27 16:28 ` dpdklab
2024-05-27 16:30 ` dpdklab
2024-05-27 16:31 ` dpdklab
2024-05-27 16:31 ` dpdklab
2024-05-27 16:31 ` dpdklab
2024-05-27 16:32 ` dpdklab
2024-05-27 16:32 ` dpdklab
2024-05-27 16:33 ` dpdklab
2024-05-27 16:36 ` dpdklab
2024-05-27 16:55 ` dpdklab
2024-05-27 16:56 ` dpdklab
2024-05-27 16:58 ` dpdklab
2024-05-27 16:59 ` dpdklab
2024-05-27 17:00 ` dpdklab
2024-05-27 17:06 ` dpdklab
2024-05-27 17:19 ` dpdklab
2024-05-27 18:46 ` dpdklab
2024-05-29 16:56 ` dpdklab
2024-05-29 17:32 ` 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=202405271451.44REpEgZ3139228@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).