From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143630-143635 [PATCH 11/11] crypto/cnxk: add PMD API to get qp stats
Date: Thu, 5 Sep 2024 15:21:28 +0800 [thread overview]
Message-ID: <202409050721.4857LSn41456075@localhost.localdomain> (raw)
In-Reply-To: <20240905074631.1462357-12-ktejasree@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143635
_Compilation OK_
Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Thu, 5 Sep 2024 13:16:21 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
143630-143635 --> 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-09-05 7:50 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240905074631.1462357-12-ktejasree@marvell.com>
2024-09-05 7:21 ` qemudev [this message]
2024-09-05 7:25 ` qemudev
2024-09-05 7:48 ` |SUCCESS| pw143635 " checkpatch
2024-09-05 8:44 ` 0-day Robot
2024-09-05 9:28 ` |PENDING| pw143630-143635 [PATCH] [11/11] crypto/cnxk: add PMD API t dpdklab
2024-09-05 9:32 ` |SUCCESS| " dpdklab
2024-09-05 9:36 ` dpdklab
2024-09-05 10:33 ` dpdklab
2024-09-05 11:54 ` dpdklab
2024-09-05 12:13 ` dpdklab
2024-09-05 12:14 ` dpdklab
2024-09-05 12:23 ` |PENDING| " dpdklab
2024-09-05 15:14 ` |SUCCESS| " dpdklab
2024-09-05 16:23 ` dpdklab
2024-09-05 16:25 ` dpdklab
2024-09-05 16:30 ` |PENDING| " dpdklab
2024-09-05 16:33 ` |SUCCESS| " dpdklab
2024-09-05 16:51 ` dpdklab
2024-09-05 16:52 ` dpdklab
2024-09-05 16:54 ` |PENDING| " dpdklab
2024-09-05 16:54 ` |SUCCESS| " dpdklab
2024-09-05 17:01 ` dpdklab
2024-09-05 17:04 ` dpdklab
2024-09-05 17:04 ` dpdklab
2024-09-05 17:04 ` dpdklab
2024-09-05 17:09 ` dpdklab
2024-09-05 17:10 ` dpdklab
2024-09-05 17:10 ` dpdklab
2024-09-05 17:10 ` dpdklab
2024-09-05 17:11 ` dpdklab
2024-09-05 17:11 ` dpdklab
2024-09-05 17:12 ` dpdklab
2024-09-05 17:12 ` dpdklab
2024-09-05 17:13 ` dpdklab
2024-09-05 17:13 ` dpdklab
2024-09-05 17:14 ` dpdklab
2024-09-05 17:15 ` dpdklab
2024-09-05 17:15 ` dpdklab
2024-09-05 17:15 ` dpdklab
2024-09-05 17:15 ` dpdklab
2024-09-05 17:16 ` dpdklab
2024-09-05 17:16 ` dpdklab
2024-09-05 17:16 ` dpdklab
2024-09-05 17:17 ` dpdklab
2024-09-05 17:17 ` dpdklab
2024-09-05 17:18 ` dpdklab
2024-09-05 17:19 ` dpdklab
2024-09-05 17:20 ` dpdklab
2024-09-05 17:20 ` dpdklab
2024-09-05 17:20 ` dpdklab
2024-09-05 17:20 ` dpdklab
2024-09-05 17:21 ` dpdklab
2024-09-05 17:22 ` dpdklab
2024-09-05 17:22 ` dpdklab
2024-09-05 17:22 ` dpdklab
2024-09-05 17:23 ` dpdklab
2024-09-05 17:23 ` dpdklab
2024-09-05 17:23 ` dpdklab
2024-09-05 17:23 ` dpdklab
2024-09-05 17:24 ` dpdklab
2024-09-05 17:24 ` dpdklab
2024-09-05 17:25 ` dpdklab
2024-09-05 17:27 ` dpdklab
2024-09-05 17:36 ` |FAILURE| " dpdklab
2024-09-05 17:37 ` dpdklab
2024-09-05 17:42 ` dpdklab
2024-09-05 17:42 ` |SUCCESS| " dpdklab
2024-09-05 17:42 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:43 ` dpdklab
2024-09-05 17:44 ` dpdklab
2024-09-05 17:44 ` dpdklab
2024-09-05 17:45 ` dpdklab
2024-09-05 17:46 ` |FAILURE| " dpdklab
2024-09-05 17:47 ` |SUCCESS| " dpdklab
2024-09-05 17:47 ` dpdklab
2024-09-05 19:31 ` dpdklab
2024-09-05 19:32 ` dpdklab
2024-09-05 19:47 ` dpdklab
2024-09-05 22:09 ` dpdklab
2024-09-05 23:09 ` dpdklab
2024-09-06 0:25 ` dpdklab
2024-09-06 23:58 ` dpdklab
2024-09-07 0:30 ` dpdklab
2024-09-18 0:51 ` dpdklab
2024-09-18 1:09 ` dpdklab
2024-09-18 1:21 ` dpdklab
2024-09-18 1:51 ` 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=202409050721.4857LSn41456075@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).