From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123904-123907 [PATCH v4 4/4] app/test-compress-perf: add algo option
Date: Wed, 15 Feb 2023 01:31:19 +0800 [thread overview]
Message-ID: <202302141731.31EHVJxg042836@localhost.localdomain> (raw)
In-Reply-To: <20230214174029.2397125-5-michaelba@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123907
_Compilation OK_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Tue, 14 Feb 2023 19:40:26 +0200
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 39d469a7eb4f157923be73aea0b0cc1015860ca7
123904-123907 --> 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-02-14 17:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230214174029.2397125-5-michaelba@nvidia.com>
2023-02-14 17:31 ` qemudev [this message]
2023-02-14 17:35 ` qemudev
2023-02-14 17:43 ` |SUCCESS| pw123907 " checkpatch
2023-02-14 19:59 ` 0-day Robot
2023-02-14 18:09 |SUCCESS| pw123904-123907 [PATCH] [v4, " dpdklab
2023-02-14 18:12 dpdklab
2023-02-14 18:13 dpdklab
2023-02-14 18:13 dpdklab
2023-02-14 18:18 dpdklab
2023-02-14 18:20 dpdklab
2023-02-14 18:24 dpdklab
2023-02-14 18:25 dpdklab
2023-02-14 18:27 dpdklab
2023-02-14 18:32 dpdklab
2023-02-14 18:35 dpdklab
2023-02-14 18:38 dpdklab
2023-02-14 18:39 dpdklab
2023-02-14 19:10 dpdklab
2023-02-14 19:10 dpdklab
2023-02-14 19:12 dpdklab
2023-02-14 19:13 dpdklab
2023-02-14 19:15 dpdklab
2023-02-14 19:16 dpdklab
2023-02-14 19:18 dpdklab
2023-02-14 19:21 dpdklab
2023-02-14 19:23 dpdklab
2023-02-14 19:25 dpdklab
2023-02-14 19:25 dpdklab
2023-02-16 9:20 dpdklab
2023-02-17 2:08 dpdklab
2023-02-18 12:06 dpdklab
2023-02-23 18:51 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=202302141731.31EHVJxg042836@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).