From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139994 [PATCH] eal/unix: support ZSTD compression for firmwares
Date: Wed, 8 May 2024 17:26:33 +0800 [thread overview]
Message-ID: <202405080926.4489QXep2253479@localhost.localdomain> (raw)
In-Reply-To: <20240508095214.2541115-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139994
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Wed, 8 May 2024 11:52:14 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139994 --> 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-05-08 9:54 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240508095214.2541115-1-david.marchand@redhat.com>
2024-05-08 9:26 ` qemudev [this message]
2024-05-08 9:31 ` qemudev
2024-05-08 9:53 ` |WARNING| " checkpatch
2024-05-08 10:44 ` |SUCCESS| " 0-day Robot
2024-05-08 12:07 ` |SUCCESS| pw139994 [PATCH] eal/unix: support ZSTD compression for fi dpdklab
2024-05-08 12:09 ` dpdklab
2024-05-08 12:10 ` dpdklab
2024-05-08 12:11 ` dpdklab
2024-05-08 12:11 ` dpdklab
2024-05-08 12:19 ` dpdklab
2024-05-08 12:36 ` dpdklab
2024-05-08 12:36 ` dpdklab
2024-05-08 12:36 ` dpdklab
2024-05-08 12:36 ` dpdklab
2024-05-08 12:37 ` dpdklab
2024-05-08 12:37 ` dpdklab
2024-05-08 12:37 ` dpdklab
2024-05-08 12:37 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:38 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:39 ` dpdklab
2024-05-08 12:40 ` dpdklab
2024-05-08 12:40 ` dpdklab
2024-05-08 12:40 ` dpdklab
2024-05-08 12:40 ` dpdklab
2024-05-08 12:41 ` dpdklab
2024-05-08 12:41 ` dpdklab
2024-05-08 12:41 ` dpdklab
2024-05-08 12:41 ` dpdklab
2024-05-08 12:42 ` dpdklab
2024-05-08 12:42 ` dpdklab
2024-05-08 12:42 ` dpdklab
2024-05-08 12:42 ` dpdklab
2024-05-08 12:42 ` dpdklab
2024-05-08 12:43 ` dpdklab
2024-05-08 12:43 ` dpdklab
2024-05-08 12:43 ` dpdklab
2024-05-08 12:43 ` dpdklab
2024-05-08 12:44 ` dpdklab
2024-05-08 12:44 ` dpdklab
2024-05-08 12:44 ` dpdklab
2024-05-08 12:45 ` dpdklab
2024-05-08 12:45 ` dpdklab
2024-05-08 12:45 ` dpdklab
2024-05-08 12:45 ` dpdklab
2024-05-08 12:46 ` dpdklab
2024-05-08 12:46 ` dpdklab
2024-05-08 12:46 ` dpdklab
2024-05-08 12:46 ` dpdklab
2024-05-08 12:46 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:47 ` dpdklab
2024-05-08 12:48 ` dpdklab
2024-05-08 12:49 ` dpdklab
2024-05-08 12:50 ` dpdklab
2024-05-08 12:51 ` dpdklab
2024-05-08 12:51 ` dpdklab
2024-05-08 12:52 ` dpdklab
2024-05-08 12:53 ` dpdklab
2024-05-08 12:54 ` dpdklab
2024-05-08 12:55 ` dpdklab
2024-05-08 12:55 ` dpdklab
2024-05-08 12:57 ` dpdklab
2024-05-08 12:59 ` dpdklab
2024-05-08 12:59 ` dpdklab
2024-05-08 12:59 ` dpdklab
2024-05-08 13:00 ` dpdklab
2024-05-08 13:03 ` dpdklab
2024-05-08 13:06 ` dpdklab
2024-05-08 13:07 ` dpdklab
2024-05-08 13:15 ` dpdklab
2024-05-08 13:22 ` dpdklab
2024-05-08 13:45 ` dpdklab
2024-05-08 13:51 ` dpdklab
2024-05-08 13:53 ` 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=202405080926.4489QXep2253479@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).