automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125034 [PATCH] mldev: remove weak symbols use in type conversions
Date: Sat, 11 Mar 2023 22:40:10 +0800	[thread overview]
Message-ID: <202303111440.32BEeAaZ3855109@localhost.localdomain> (raw)
In-Reply-To: <20230311145056.16386-1-syalavarthi@marvell.com>

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

_Compilation OK_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Sat, 11 Mar 2023 06:50:56 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 0fd1386c30c3ad9365d7fdd2829bf7cb2e1b9dff

125034 --> 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-03-11 14:54 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230311145056.16386-1-syalavarthi@marvell.com>
2023-03-11 14:40 ` qemudev [this message]
2023-03-11 14:44 ` qemudev
2023-03-11 14:52 ` checkpatch
2023-03-11 16:59 ` 0-day Robot
2023-03-11 21:16 dpdklab
2023-03-11 21:20 dpdklab
2023-03-11 21:23 dpdklab
2023-03-11 21:24 dpdklab
2023-03-11 21:26 dpdklab
2023-03-11 21:28 dpdklab
2023-03-11 21:28 dpdklab
2023-03-11 21:34 dpdklab
2023-03-11 21:35 dpdklab
2023-03-11 21:37 dpdklab
2023-03-11 21:39 dpdklab
2023-03-11 21:44 dpdklab
2023-03-11 21:47 dpdklab
2023-03-11 21:55 dpdklab
2023-03-11 21:57 dpdklab
2023-03-11 22:01 dpdklab
2023-03-11 22:01 dpdklab
2023-03-11 22:08 dpdklab
2023-03-11 22:09 dpdklab
2023-03-11 22:11 dpdklab
2023-03-11 22:12 dpdklab
2023-03-11 22:12 dpdklab
2023-03-11 22:13 dpdklab
2023-03-11 22:14 dpdklab
2023-03-11 22:16 dpdklab
2023-03-11 22:22 dpdklab
2023-03-11 22:27 dpdklab
2023-03-11 23:37 dpdklab
2023-03-12 17:13 dpdklab
2023-03-12 18:19 dpdklab
2023-03-12 18:59 dpdklab
2023-03-12 19:49 dpdklab
2023-03-13  4:49 dpdklab
2023-03-13  4:52 dpdklab
2023-03-13  4:52 dpdklab
2023-03-13  4:53 dpdklab
2023-03-13  4:57 dpdklab
2023-03-13  4:59 dpdklab
2023-03-13  5:14 dpdklab
2023-03-13  5:17 dpdklab
2023-03-13  5:24 dpdklab
2023-03-13  5:29 dpdklab
2023-03-13  5:32 dpdklab
2023-03-13  5:32 dpdklab
2023-03-13  5:33 dpdklab
2023-03-13  5:44 dpdklab
2023-03-13  5:48 dpdklab
2023-03-13  5:49 dpdklab
2023-03-13  5:49 dpdklab
2023-03-13  5:55 dpdklab
2023-03-13  5:58 dpdklab
2023-03-13  5:59 dpdklab
2023-03-13  6:03 dpdklab
2023-03-13  6:04 dpdklab
2023-03-13  6:04 dpdklab
2023-03-13  6:06 dpdklab
2023-03-13  6:15 dpdklab
2023-03-13  6:19 dpdklab
2023-03-13  6:37 dpdklab
2023-03-13  6:38 dpdklab
2023-03-13 22:46 dpdklab
2023-03-14  0:18 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=202303111440.32BEeAaZ3855109@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).