automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133710 [PATCH] ethdev: fix 32-bit build with GCC-13
Date: Wed, 1 Nov 2023 14:58:13 +0800	[thread overview]
Message-ID: <202311010658.3A16wDD5708138@localhost.localdomain> (raw)
In-Reply-To: <20231101071554.1316358-1-ruifeng.wang@arm.com>

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

_Compilation OK_

Submitter: Ruifeng Wang <ruifeng.wang@arm.com>
Date: Wed,  1 Nov 2023 15:15:54 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: a3ae1f9cddd20e65b90b5606f846f46175a50181

133710 --> 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-11-01  7:19 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231101071554.1316358-1-ruifeng.wang@arm.com>
2023-11-01  6:58 ` qemudev [this message]
2023-11-01  7:02 ` qemudev
2023-11-01  7:18 ` |WARNING| " checkpatch
2023-11-01  8:19 ` |SUCCESS| " 0-day Robot
2023-11-01 16:41 dpdklab
2023-11-01 16:41 dpdklab
2023-11-01 16:44 dpdklab
2023-11-01 16:45 dpdklab
2023-11-01 16:47 dpdklab
2023-11-01 16:49 dpdklab
2023-11-01 16:49 dpdklab
2023-11-01 16:51 dpdklab
2023-11-01 17:00 dpdklab
2023-11-01 17:27 dpdklab
2023-11-01 17:39 dpdklab
2023-11-01 17:40 dpdklab
2023-11-01 17:42 dpdklab
2023-11-01 17:42 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:43 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:44 dpdklab
2023-11-01 17:45 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:48 dpdklab
2023-11-01 17:51 dpdklab
2023-11-01 18:00 dpdklab
2023-11-01 18:05 dpdklab
2023-11-01 18:05 dpdklab
2023-11-01 18:06 dpdklab
2023-11-01 18:06 dpdklab
2023-11-01 18:07 dpdklab
2023-11-01 18:07 dpdklab
2023-11-01 18:07 dpdklab
2023-11-01 18:08 dpdklab
2023-11-01 18:08 dpdklab
2023-11-01 18:08 dpdklab
2023-11-01 18:09 dpdklab
2023-11-01 18:09 dpdklab
2023-11-01 18:09 dpdklab
2023-11-01 18:12 dpdklab
2023-11-01 18:55 dpdklab
2023-11-01 18:56 dpdklab
2023-11-01 19:52 dpdklab
2023-11-01 20:27 dpdklab
2023-11-01 22:28 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=202311010658.3A16wDD5708138@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).