From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122297 [PATCH v2] eventdev/crypto: fix missing crypto vec limits
Date: Wed, 18 Jan 2023 18:13:58 +0800 [thread overview]
Message-ID: <202301181013.30IADw9x2118709@localhost.localdomain> (raw)
In-Reply-To: <20230118102148.233481-1-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122297
_Compilation OK_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Wed, 18 Jan 2023 11:21:47 +0100
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: dddeb1ca2742ceaa9dd9b7f4def0d7bbab53378f
122297 --> 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:[~2023-01-18 10:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230118102148.233481-1-vfialko@marvell.com>
2023-01-18 10:13 ` qemudev [this message]
2023-01-18 10:17 ` qemudev
2023-01-18 10:22 ` checkpatch
2023-01-18 11:19 ` 0-day Robot
2023-01-19 6:12 |SUCCESS| pw122297 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-01-19 1:37 dpdklab
2023-01-19 0:52 dpdklab
2023-01-19 0:52 dpdklab
2023-01-19 0:52 dpdklab
2023-01-19 0:52 dpdklab
2023-01-19 0:52 dpdklab
2023-01-19 0:51 dpdklab
2023-01-19 0:51 dpdklab
2023-01-19 0:51 dpdklab
2023-01-18 12:10 dpdklab
2023-01-18 11:31 dpdklab
2023-01-18 11:29 dpdklab
2023-01-18 11:09 dpdklab
2023-01-18 11:05 dpdklab
2023-01-18 10:58 dpdklab
2023-01-18 10:56 dpdklab
2023-01-18 10:55 dpdklab
2023-01-18 10:54 dpdklab
2023-01-18 10:53 dpdklab
2023-01-18 10:49 dpdklab
2023-01-18 10:48 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=202301181013.30IADw9x2118709@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).