automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124124 [PATCH] net/mlx5: fix build failure on Windows
Date: Fri, 17 Feb 2023 22:26:11 +0800	[thread overview]
Message-ID: <202302171426.31HEQBgP2203696@localhost.localdomain> (raw)
In-Reply-To: <20230217143717.203737-1-maxime.coquelin@redhat.com>

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

_Compilation OK_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Fri, 17 Feb 2023 15:37:17 +0100
DPDK git baseline: Repo:dpdk-next-net-mlx
  Branch: for-next-net
  CommitID: 1a9c4a9c127560a6ecb9f0514998bce225acb7d5

124124 --> 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-02-17 14:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230217143717.203737-1-maxime.coquelin@redhat.com>
2023-02-17 14:26 ` qemudev [this message]
2023-02-17 14:30 ` qemudev
2023-02-17 14:38 ` |WARNING| " checkpatch
2023-02-17 17:19 ` |SUCCESS| " 0-day Robot
2023-02-17 15:08 dpdklab
2023-02-17 15:10 dpdklab
2023-02-17 15:13 dpdklab
2023-02-17 15:15 dpdklab
2023-02-17 15:15 dpdklab
2023-02-17 15:25 dpdklab
2023-02-17 15:37 dpdklab
2023-02-17 15:43 dpdklab
2023-02-17 15:53 dpdklab
2023-02-17 15:55 dpdklab
2023-02-17 15:57 dpdklab
2023-02-17 16:01 dpdklab
2023-02-17 16:02 dpdklab
2023-02-17 16:02 dpdklab
2023-02-17 16:04 dpdklab
2023-02-17 16:09 dpdklab
2023-02-17 16:13 dpdklab
2023-02-17 16:17 dpdklab
2023-02-17 16:17 dpdklab
2023-02-18 12:28 dpdklab
2023-02-19 19:54 dpdklab
2023-02-24 23:20 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=202302171426.31HEQBgP2203696@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).