From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139178-139179 [PATCH 2/2] dma/cnxk: remove completion pool
Date: Sat, 6 Apr 2024 17:50:58 +0800 [thread overview]
Message-ID: <202404060950.4369ow0J3518440@localhost.localdomain> (raw)
In-Reply-To: <20240406101311.11044-2-pbhagavatula@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139179
_Compilation OK_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Sat, 6 Apr 2024 15:43:10 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139178-139179 --> 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-04-06 10:15 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240406101311.11044-2-pbhagavatula@marvell.com>
2024-04-06 9:50 ` qemudev [this message]
2024-04-06 9:55 ` qemudev
2024-04-06 10:15 ` |SUCCESS| pw139179 " checkpatch
2024-04-06 11:03 ` |FAILURE| " 0-day Robot
2024-04-06 11:07 ` |SUCCESS| pw139178-139179 [PATCH] [2/2] dma/cnxk: remove completion dpdklab
2024-04-06 11:07 ` dpdklab
2024-04-06 11:08 ` dpdklab
2024-04-06 11:08 ` dpdklab
2024-04-06 11:13 ` dpdklab
2024-04-06 11:13 ` dpdklab
2024-04-06 11:13 ` |FAILURE| " dpdklab
2024-04-06 11:13 ` |SUCCESS| " dpdklab
2024-04-06 11:14 ` dpdklab
2024-04-06 11:14 ` dpdklab
2024-04-06 11:14 ` dpdklab
2024-04-06 11:15 ` dpdklab
2024-04-06 11:15 ` dpdklab
2024-04-06 11:15 ` dpdklab
2024-04-06 11:16 ` dpdklab
2024-04-06 11:16 ` dpdklab
2024-04-06 11:17 ` dpdklab
2024-04-06 11:17 ` dpdklab
2024-04-06 11:17 ` dpdklab
2024-04-06 11:17 ` dpdklab
2024-04-06 11:18 ` |FAILURE| " dpdklab
2024-04-06 11:18 ` |SUCCESS| " dpdklab
2024-04-06 11:18 ` |FAILURE| " dpdklab
2024-04-06 11:18 ` |SUCCESS| " dpdklab
2024-04-06 11:18 ` dpdklab
2024-04-06 11:19 ` |FAILURE| " dpdklab
2024-04-06 11:19 ` |SUCCESS| " dpdklab
2024-04-06 11:19 ` |FAILURE| " dpdklab
2024-04-06 11:19 ` |SUCCESS| " dpdklab
2024-04-06 11:20 ` |FAILURE| " dpdklab
2024-04-06 11:20 ` dpdklab
2024-04-06 11:20 ` |SUCCESS| " dpdklab
2024-04-06 11:20 ` |FAILURE| " dpdklab
2024-04-06 11:20 ` dpdklab
2024-04-06 11:20 ` |SUCCESS| " dpdklab
2024-04-06 11:20 ` dpdklab
2024-04-06 11:22 ` dpdklab
2024-04-06 11:23 ` dpdklab
2024-04-06 11:24 ` dpdklab
2024-04-06 11:24 ` dpdklab
2024-04-06 11:24 ` dpdklab
2024-04-06 11:24 ` |FAILURE| " dpdklab
2024-04-06 11:25 ` |SUCCESS| " dpdklab
2024-04-06 11:25 ` dpdklab
2024-04-06 11:25 ` dpdklab
2024-04-06 11:25 ` dpdklab
2024-04-06 11:30 ` dpdklab
2024-04-06 11:31 ` dpdklab
2024-04-06 11:32 ` dpdklab
2024-04-06 11:33 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:34 ` dpdklab
2024-04-06 11:35 ` dpdklab
2024-04-06 11:35 ` dpdklab
2024-04-06 11:36 ` dpdklab
2024-04-06 11:37 ` dpdklab
2024-04-06 11:37 ` |FAILURE| " dpdklab
2024-04-06 11:38 ` |SUCCESS| " dpdklab
2024-04-06 11:38 ` dpdklab
2024-04-06 11:39 ` dpdklab
2024-04-06 11:39 ` dpdklab
2024-04-06 11:39 ` dpdklab
2024-04-06 11:39 ` dpdklab
2024-04-06 11:40 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:43 ` dpdklab
2024-04-06 11:43 ` dpdklab
2024-04-06 11:45 ` dpdklab
2024-04-06 11:58 ` dpdklab
2024-04-06 12:00 ` dpdklab
2024-04-06 12:04 ` |FAILURE| " dpdklab
2024-04-06 12:05 ` |SUCCESS| " dpdklab
2024-04-06 12:13 ` dpdklab
2024-04-06 12:20 ` dpdklab
2024-04-06 12:44 ` |FAILURE| " dpdklab
2024-04-06 12:50 ` 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=202404060950.4369ow0J3518440@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).