From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137991 [PATCH] test/crypto: fix non ASCII character
Date: Tue, 5 Mar 2024 19:11:49 +0800 [thread overview]
Message-ID: <202403051111.425BBnkw2007890@localhost.localdomain> (raw)
In-Reply-To: <20240305113428.365-1-anoobj@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137991
_Compilation OK_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Tue, 5 Mar 2024 17:04:28 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: be793709e7b044cd4f806d6103bf3c046311a3c7
137991 --> 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-03-05 11:36 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240305113428.365-1-anoobj@marvell.com>
2024-03-05 11:11 ` qemudev [this message]
2024-03-05 11:16 ` qemudev
2024-03-05 11:35 ` checkpatch
2024-03-05 12:25 ` 0-day Robot
2024-03-05 12:31 ` dpdklab
2024-03-05 12:32 ` dpdklab
2024-03-05 12:34 ` dpdklab
2024-03-05 12:34 ` dpdklab
2024-03-05 12:35 ` dpdklab
2024-03-05 12:37 ` dpdklab
2024-03-05 13:02 ` dpdklab
2024-03-05 13:02 ` dpdklab
2024-03-05 13:06 ` dpdklab
2024-03-05 13:06 ` dpdklab
2024-03-05 13:07 ` dpdklab
2024-03-05 13:15 ` dpdklab
2024-03-05 13:15 ` dpdklab
2024-03-05 13:16 ` dpdklab
2024-03-05 13:16 ` dpdklab
2024-03-05 13:16 ` dpdklab
2024-03-05 13:16 ` dpdklab
2024-03-05 13:17 ` dpdklab
2024-03-05 13:17 ` dpdklab
2024-03-05 13:17 ` dpdklab
2024-03-05 13:18 ` dpdklab
2024-03-05 13:20 ` dpdklab
2024-03-05 13:20 ` dpdklab
2024-03-05 13:20 ` dpdklab
2024-03-05 13:21 ` dpdklab
2024-03-05 13:21 ` dpdklab
2024-03-05 13:21 ` dpdklab
2024-03-05 13:22 ` dpdklab
2024-03-05 13:22 ` dpdklab
2024-03-05 13:23 ` dpdklab
2024-03-05 13:23 ` dpdklab
2024-03-05 13:23 ` dpdklab
2024-03-05 13:23 ` dpdklab
2024-03-05 13:24 ` dpdklab
2024-03-05 13:24 ` dpdklab
2024-03-05 13:24 ` dpdklab
2024-03-05 13:25 ` dpdklab
2024-03-05 13:25 ` dpdklab
2024-03-05 13:25 ` dpdklab
2024-03-05 13:25 ` dpdklab
2024-03-05 13:25 ` dpdklab
2024-03-05 13:26 ` dpdklab
2024-03-05 13:27 ` dpdklab
2024-03-05 13:27 ` dpdklab
2024-03-05 13:27 ` dpdklab
2024-03-05 13:27 ` dpdklab
2024-03-05 13:28 ` dpdklab
2024-03-05 13:39 ` dpdklab
2024-03-05 13:46 ` dpdklab
2024-03-05 13:48 ` dpdklab
2024-03-05 13:52 ` dpdklab
2024-03-05 13:53 ` dpdklab
2024-03-05 13:54 ` dpdklab
2024-03-05 13:54 ` dpdklab
2024-03-05 13:54 ` dpdklab
2024-03-05 13:55 ` dpdklab
2024-03-05 13:57 ` dpdklab
2024-03-05 13:57 ` dpdklab
2024-03-05 13:59 ` dpdklab
2024-03-05 14:01 ` dpdklab
2024-03-05 14:02 ` dpdklab
2024-03-05 14:06 ` dpdklab
2024-03-05 14:13 ` dpdklab
2024-03-05 14:22 ` dpdklab
2024-03-05 14:45 ` dpdklab
2024-03-05 14:57 ` dpdklab
2024-03-09 4:30 ` dpdklab
2024-03-09 5:07 ` dpdklab
2024-03-09 5:45 ` 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=202403051111.425BBnkw2007890@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).