automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125062 [PATCH] reorder: fix registration of dynamic field in mbuf
Date: Mon, 13 Mar 2023 17:27:06 +0800	[thread overview]
Message-ID: <202303130927.32D9R6fR431510@localhost.localdomain> (raw)
In-Reply-To: <20230313093450.2560058-1-vfialko@marvell.com>

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

_Compilation OK_

Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Mon, 13 Mar 2023 10:34:50 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: baf13c3135d0c5998fff7edc23fb89412dc89246

125062 --> 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-13  9:41 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230313093450.2560058-1-vfialko@marvell.com>
2023-03-13  9:27 ` qemudev [this message]
2023-03-13  9:30 ` qemudev
2023-03-13  9:36 ` checkpatch
2023-03-13 11:19 ` 0-day Robot
2023-03-13 11:44 dpdklab
2023-03-13 11:47 dpdklab
2023-03-13 11:52 dpdklab
2023-03-13 11:55 dpdklab
2023-03-13 11:55 dpdklab
2023-03-13 11:59 dpdklab
2023-03-13 11:59 dpdklab
2023-03-13 12:01 dpdklab
2023-03-13 12:03 dpdklab
2023-03-13 12:07 dpdklab
2023-03-13 12:11 dpdklab
2023-03-13 12:59 dpdklab
2023-03-13 13:09 dpdklab
2023-03-13 13:09 dpdklab
2023-03-13 13:09 dpdklab
2023-03-13 13:11 dpdklab
2023-03-13 13:12 dpdklab
2023-03-13 13:12 dpdklab
2023-03-13 13:16 dpdklab
2023-03-13 13:17 dpdklab
2023-03-13 13:19 dpdklab
2023-03-13 13:21 dpdklab
2023-03-13 13:26 dpdklab
2023-03-13 13:30 dpdklab
2023-03-13 13:38 dpdklab
2023-03-13 13:38 dpdklab
2023-03-13 13:43 dpdklab
2023-03-13 14:25 dpdklab
2023-03-13 14:45 dpdklab
2023-03-13 16:42 dpdklab
2023-03-13 16:48 dpdklab
2023-03-14  0:58 dpdklab
2023-03-14  1:10 dpdklab
2023-03-14  1:11 dpdklab
2023-03-14  1:16 dpdklab
2023-03-14  1:19 dpdklab
2023-03-14  1:23 dpdklab
2023-03-14  1:23 dpdklab
2023-03-14  1:24 dpdklab
2023-03-14  1:26 dpdklab
2023-03-14  1:27 dpdklab
2023-03-14  1:28 dpdklab
2023-03-14  1:58 dpdklab
2023-03-14  2:03 dpdklab
2023-03-14  2:19 dpdklab
2023-03-14  2:19 dpdklab
2023-03-14  2:22 dpdklab
2023-03-14  2:28 dpdklab
2023-03-14  2:31 dpdklab
2023-03-14  2:32 dpdklab
2023-03-14  2:34 dpdklab
2023-03-14  2:35 dpdklab
2023-03-14  2:37 dpdklab
2023-03-14  2:40 dpdklab
2023-03-14  2:42 dpdklab
2023-03-14  3:22 dpdklab
2023-03-14  3:23 dpdklab
2023-03-14 23:34 dpdklab
2023-03-15  0:40 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=202303130927.32D9R6fR431510@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).