From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140323 [PATCH v2] dma/cnxk: add higher chunk size support
Date: Mon, 27 May 2024 19:58:37 +0800 [thread overview]
Message-ID: <202405271158.44RBwbHo2904979@localhost.localdomain> (raw)
In-Reply-To: <20240527122401.5954-1-pbhagavatula@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140323
_Compilation OK_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Mon, 27 May 2024 17:54:01 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: 9c01593375aff7266a6c0b209bd4d0363c3b7b84
140323 --> 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 12:27 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240527122401.5954-1-pbhagavatula@marvell.com>
2024-05-27 11:58 ` qemudev [this message]
2024-05-27 12:03 ` qemudev
2024-05-27 12:25 ` checkpatch
2024-05-27 13:43 ` 0-day Robot
2024-05-27 14:07 ` |SUCCESS| pw140323 [PATCH] [v2] dma/cnxk: add higher chunk size supp dpdklab
2024-05-27 14:08 ` dpdklab
2024-05-27 14:09 ` dpdklab
2024-05-27 14:09 ` dpdklab
2024-05-27 14:09 ` dpdklab
2024-05-27 14:10 ` dpdklab
2024-05-27 14:10 ` dpdklab
2024-05-27 14:10 ` dpdklab
2024-05-27 14:10 ` dpdklab
2024-05-27 14:10 ` dpdklab
2024-05-27 14:11 ` dpdklab
2024-05-27 14:11 ` dpdklab
2024-05-27 14:11 ` dpdklab
2024-05-27 14:12 ` dpdklab
2024-05-27 14:12 ` dpdklab
2024-05-27 14:12 ` dpdklab
2024-05-27 14:12 ` dpdklab
2024-05-27 14:13 ` dpdklab
2024-05-27 14:14 ` dpdklab
2024-05-27 14:14 ` dpdklab
2024-05-27 14:14 ` dpdklab
2024-05-27 14:14 ` dpdklab
2024-05-27 14:15 ` dpdklab
2024-05-27 14:18 ` dpdklab
2024-05-27 14:18 ` dpdklab
2024-05-27 14:19 ` dpdklab
2024-05-27 14:20 ` dpdklab
2024-05-27 14:21 ` dpdklab
2024-05-27 14:21 ` dpdklab
2024-05-27 14:21 ` dpdklab
2024-05-27 14:22 ` dpdklab
2024-05-27 14:22 ` dpdklab
2024-05-27 14:22 ` dpdklab
2024-05-27 14:22 ` dpdklab
2024-05-27 14:23 ` dpdklab
2024-05-27 14:24 ` dpdklab
2024-05-27 14:24 ` dpdklab
2024-05-27 14:25 ` dpdklab
2024-05-27 14:25 ` dpdklab
2024-05-27 14:26 ` dpdklab
2024-05-27 14:26 ` dpdklab
2024-05-27 14:26 ` dpdklab
2024-05-27 14:28 ` dpdklab
2024-05-27 14:29 ` dpdklab
2024-05-27 14:30 ` dpdklab
2024-05-27 14:30 ` |FAILURE| " dpdklab
2024-05-27 14:31 ` |SUCCESS| " dpdklab
2024-05-27 14:31 ` |FAILURE| " dpdklab
2024-05-27 14:32 ` |SUCCESS| " dpdklab
2024-05-27 14:33 ` dpdklab
2024-05-27 14:33 ` dpdklab
2024-05-27 14:35 ` dpdklab
2024-05-27 14:36 ` dpdklab
2024-05-27 14:36 ` |FAILURE| " dpdklab
2024-05-27 14:41 ` |SUCCESS| " dpdklab
2024-05-27 14:41 ` |FAILURE| " dpdklab
2024-05-27 14:41 ` |SUCCESS| " dpdklab
2024-05-27 14:41 ` |FAILURE| " dpdklab
2024-05-27 14:42 ` dpdklab
2024-05-27 14:45 ` |SUCCESS| " dpdklab
2024-05-27 14:46 ` dpdklab
2024-05-27 14:46 ` dpdklab
2024-05-27 14:46 ` dpdklab
2024-05-27 14:47 ` dpdklab
2024-05-27 14:49 ` dpdklab
2024-05-27 14:49 ` dpdklab
2024-05-27 14:50 ` dpdklab
2024-05-27 14:52 ` dpdklab
2024-05-27 14:52 ` dpdklab
2024-05-27 14:52 ` |FAILURE| " dpdklab
2024-05-27 14:53 ` dpdklab
2024-05-27 14:53 ` dpdklab
2024-05-27 14:54 ` |SUCCESS| " dpdklab
2024-05-27 14:55 ` |FAILURE| " dpdklab
2024-05-27 14:56 ` dpdklab
2024-05-27 14:56 ` |SUCCESS| " dpdklab
2024-05-27 14:58 ` dpdklab
2024-05-27 15:00 ` dpdklab
2024-05-27 15:01 ` |FAILURE| " dpdklab
2024-05-27 15:02 ` |SUCCESS| " dpdklab
2024-05-27 15:05 ` dpdklab
2024-05-27 15:08 ` dpdklab
2024-05-27 15:19 ` dpdklab
2024-05-27 15:32 ` dpdklab
2024-05-27 15:33 ` dpdklab
2024-05-29 16:17 ` dpdklab
2024-05-29 16:43 ` 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=202405271158.44RBwbHo2904979@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).