automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121495 [PATCH] compressdev: fix end of comp PMD list macro conflict
Date: Sun, 1 Jan 2023 21:39:48 +0800	[thread overview]
Message-ID: <202301011339.301DdmKg1621345@localhost.localdomain> (raw)
In-Reply-To: <20230101134720.1709991-1-michaelba@nvidia.com>

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

_Compilation OK_

Submitter: Michael Baum <michaelba@nvidia.com>
Date: Sun, 1 Jan 2023 15:47:20 +0200
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: c581c49cd3fcaff596fbe566e270b442e6326c79

121495 --> 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:[~2023-01-01 13:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230101134720.1709991-1-michaelba@nvidia.com>
2023-01-01 13:39 ` qemudev [this message]
2023-01-01 13:43 ` qemudev
2023-01-01 13:49 ` checkpatch
2023-01-01 14:59 ` 0-day Robot
2023-01-01 14:20 dpdklab
2023-01-01 14:25 dpdklab
2023-01-01 14:29 dpdklab
2023-01-01 14:33 dpdklab
2023-01-01 14:36 dpdklab
2023-01-01 14:40 dpdklab
2023-01-01 14:56 dpdklab
2023-01-01 15:18 dpdklab
2023-01-01 15:23 dpdklab
2023-01-01 15:24 dpdklab
2023-01-01 15:32 dpdklab
2023-01-01 15:33 dpdklab
2023-01-01 15:34 dpdklab
2023-01-01 15:39 dpdklab
2023-01-01 15:39 dpdklab
2023-01-01 15:42 dpdklab
2023-01-01 15:44 dpdklab
2023-01-01 15:50 dpdklab
2023-01-01 15:52 dpdklab
2023-01-01 15:54 dpdklab
2023-01-01 15:54 dpdklab
2023-01-01 16:04 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=202301011339.301DdmKg1621345@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).