From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125105 [PATCH] crypto/cnxk: update number of max capabilities
Date: Wed, 15 Mar 2023 08:43:57 +0800 [thread overview]
Message-ID: <202303150043.32F0hv363171893@localhost.localdomain> (raw)
In-Reply-To: <20230314140109.3024760-1-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125105
_Compilation OK_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Tue, 14 Mar 2023 15:01:09 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: baf13c3135d0c5998fff7edc23fb89412dc89246
125105 --> 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 prev parent reply other threads:[~2023-03-15 0:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230314140109.3024760-1-vfialko@marvell.com>
2023-03-14 14:02 ` checkpatch
2023-03-14 16:39 ` 0-day Robot
2023-03-15 0:43 ` qemudev [this message]
2023-03-15 0:44 ` qemudev
2023-03-16 18:34 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-16 0:24 dpdklab
2023-03-16 0:23 dpdklab
2023-03-16 0:18 dpdklab
2023-03-16 0:14 dpdklab
2023-03-16 0:11 dpdklab
2023-03-16 0:04 dpdklab
2023-03-16 0:00 dpdklab
2023-03-15 23:53 dpdklab
2023-03-15 23:50 dpdklab
2023-03-15 23:43 dpdklab
2023-03-15 23:37 dpdklab
2023-03-15 22:48 dpdklab
2023-03-15 1:27 dpdklab
2023-03-15 1:06 dpdklab
2023-03-14 19:53 dpdklab
2023-03-14 18:08 dpdklab
2023-03-14 17:48 dpdklab
2023-03-14 17:45 dpdklab
2023-03-14 17:36 dpdklab
2023-03-14 17:33 dpdklab
2023-03-14 17:30 dpdklab
2023-03-14 17:29 dpdklab
2023-03-14 17:26 dpdklab
2023-03-14 17:22 dpdklab
2023-03-14 17:20 dpdklab
2023-03-14 17:18 dpdklab
2023-03-14 17:17 dpdklab
2023-03-14 17:13 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=202303150043.32F0hv363171893@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).