From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121703 [PATCH v2] crypto/openssl: fix warning on copy length
Date: Mon, 9 Jan 2023 11:33:17 +0800 [thread overview]
Message-ID: <202301090333.3093XHud941932@localhost.localdomain> (raw)
In-Reply-To: <20230109034021.2759215-1-ruifeng.wang@arm.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121703
_Compilation OK_
Submitter: Ruifeng Wang <ruifeng.wang@arm.com>
Date: Mon, 9 Jan 2023 11:40:21 +0800
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: be8e5d957366be70335cb04d75978723f994bdee
121703 --> 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-09 3:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230109034021.2759215-1-ruifeng.wang@arm.com>
2023-01-09 3:33 ` qemudev [this message]
2023-01-09 3:37 ` qemudev
2023-01-09 3:40 ` |WARNING| " checkpatch
2023-01-09 4:59 ` |FAILURE| " 0-day Robot
2023-01-09 4:10 |SUCCESS| pw121703 [PATCH] [v2] " dpdklab
2023-01-09 4:11 dpdklab
2023-01-09 4:15 dpdklab
2023-01-09 4:17 dpdklab
2023-01-09 4:23 dpdklab
2023-01-09 4:26 dpdklab
2023-01-09 4:30 dpdklab
2023-01-09 4:31 dpdklab
2023-01-09 4:54 dpdklab
2023-01-09 5:23 dpdklab
2023-01-09 5:23 dpdklab
2023-01-09 5:23 dpdklab
2023-01-09 5:56 dpdklab
2023-01-09 6:00 dpdklab
2023-01-09 6:23 dpdklab
2023-01-09 6:23 dpdklab
2023-01-09 6:23 dpdklab
2023-01-09 6:23 dpdklab
2023-01-09 6:27 dpdklab
2023-01-09 6:28 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=202301090333.3093XHud941932@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).