automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140029 [PATCH v2] eal/unix: support ZSTD compression for firmware
Date: Mon, 13 May 2024 18:46:58 +0800	[thread overview]
Message-ID: <202405131046.44DAkwrq2697265@localhost.localdomain> (raw)
In-Reply-To: <20240513111204.3120460-1-david.marchand@redhat.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140029

_Compilation OK_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Mon, 13 May 2024 13:12:04 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

140029 --> 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


       reply	other threads:[~2024-05-13 11:14 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240513111204.3120460-1-david.marchand@redhat.com>
2024-05-13 10:46 ` qemudev [this message]
2024-05-13 10:51 ` qemudev
2024-05-13 11:12 ` checkpatch
2024-05-13 12:03 ` 0-day Robot
2024-05-13 17:25 ` |SUCCESS| pw140029 [PATCH] [v2] eal/unix: support ZSTD compression f dpdklab
2024-05-13 17:25 ` dpdklab
2024-05-13 17:26 ` dpdklab
2024-05-13 17:26 ` dpdklab
2024-05-13 17:26 ` dpdklab
2024-05-13 17:26 ` dpdklab
2024-05-13 17:26 ` dpdklab
2024-05-13 17:27 ` dpdklab
2024-05-13 17:27 ` dpdklab
2024-05-13 17:27 ` dpdklab
2024-05-13 17:27 ` dpdklab
2024-05-13 17:27 ` dpdklab
2024-05-13 17:28 ` dpdklab
2024-05-13 17:28 ` dpdklab
2024-05-13 17:28 ` dpdklab
2024-05-13 17:28 ` dpdklab
2024-05-13 17:28 ` dpdklab
2024-05-13 17:29 ` dpdklab
2024-05-13 17:29 ` dpdklab
2024-05-13 17:30 ` dpdklab
2024-05-13 17:30 ` dpdklab
2024-05-13 17:30 ` dpdklab
2024-05-13 17:30 ` dpdklab
2024-05-13 17:31 ` dpdklab
2024-05-13 17:31 ` dpdklab
2024-05-13 17:31 ` dpdklab
2024-05-13 17:31 ` dpdklab
2024-05-13 17:32 ` dpdklab
2024-05-13 17:32 ` dpdklab
2024-05-13 17:32 ` dpdklab
2024-05-13 17:32 ` dpdklab
2024-05-13 17:32 ` dpdklab
2024-05-13 17:32 ` dpdklab
2024-05-13 17:33 ` dpdklab
2024-05-13 17:33 ` dpdklab
2024-05-13 17:33 ` dpdklab
2024-05-13 17:33 ` dpdklab
2024-05-13 17:34 ` dpdklab
2024-05-13 17:34 ` dpdklab
2024-05-13 17:35 ` dpdklab
2024-05-13 17:35 ` dpdklab
2024-05-13 17:35 ` dpdklab
2024-05-13 17:35 ` dpdklab
2024-05-13 17:35 ` dpdklab
2024-05-13 17:35 ` dpdklab
2024-05-13 17:35 ` dpdklab
2024-05-13 17:38 ` dpdklab
2024-05-13 17:38 ` dpdklab
2024-05-13 17:39 ` dpdklab
2024-05-13 17:39 ` dpdklab
2024-05-13 17:39 ` dpdklab
2024-05-13 17:40 ` dpdklab
2024-05-13 17:42 ` dpdklab
2024-05-13 17:43 ` dpdklab
2024-05-13 17:43 ` dpdklab
2024-05-13 17:43 ` dpdklab
2024-05-13 17:43 ` dpdklab
2024-05-13 17:43 ` dpdklab
2024-05-13 17:44 ` dpdklab
2024-05-13 17:44 ` dpdklab
2024-05-13 17:45 ` dpdklab
2024-05-13 17:46 ` dpdklab
2024-05-13 17:46 ` dpdklab
2024-05-13 17:46 ` dpdklab
2024-05-13 17:47 ` dpdklab
2024-05-13 17:49 ` dpdklab
2024-05-13 17:52 ` dpdklab
2024-05-13 17:52 ` dpdklab
2024-05-13 17:52 ` dpdklab
2024-05-13 17:53 ` dpdklab
2024-05-13 17:58 ` dpdklab
2024-05-13 17:59 ` dpdklab
2024-05-13 18:00 ` dpdklab
2024-05-13 18:02 ` dpdklab
2024-05-13 18:11 ` dpdklab
2024-05-13 18:11 ` dpdklab
2024-05-13 18:17 ` dpdklab
2024-05-13 18:20 ` dpdklab
2024-05-13 18:21 ` dpdklab
2024-05-13 18:25 ` dpdklab
2024-05-13 18:29 ` dpdklab
2024-05-13 18:44 ` dpdklab
2024-05-13 19:00 ` dpdklab
2024-05-13 20:22 ` 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=202405131046.44DAkwrq2697265@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).