From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120476 [PATCH] build: fix missing crypto vec limits in version
Date: Fri, 9 Dec 2022 01:09:47 +0800 [thread overview]
Message-ID: <202212081709.2B8H9lbL200087@localhost.localdomain> (raw)
In-Reply-To: <20221206092329.2250774-1-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/120476
_Compilation OK_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Tue, 6 Dec 2022 10:23:29 +0100
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562
120476 --> 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:[~2022-12-12 11:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221206092329.2250774-1-vfialko@marvell.com>
2022-12-06 9:24 ` |WARNING| " checkpatch
2022-12-06 11:18 ` |SUCCESS| " 0-day Robot
2022-12-08 16:33 ` qemudev
2022-12-08 16:34 ` qemudev
2022-12-08 17:09 ` qemudev [this message]
2022-12-08 17:10 ` qemudev
2022-12-10 0:58 ` qemudev
2022-12-10 0:59 ` qemudev
2022-12-06 9:50 dpdklab
2022-12-06 9:51 dpdklab
2022-12-06 9:56 dpdklab
2022-12-06 9:59 dpdklab
2022-12-06 10:06 dpdklab
2022-12-06 10:10 dpdklab
2022-12-06 10:37 dpdklab
2022-12-06 11:00 dpdklab
2022-12-06 11:00 dpdklab
2022-12-06 11:00 dpdklab
2022-12-06 11:18 dpdklab
2022-12-06 11:18 dpdklab
2022-12-06 11:18 dpdklab
2022-12-06 11:32 dpdklab
2022-12-06 11:33 dpdklab
2022-12-06 11:33 dpdklab
2022-12-06 14:40 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=202212081709.2B8H9lbL200087@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).