From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125070 [PATCH v2] reorder: fix registration of dynamic field in mbuf
Date: Mon, 13 Mar 2023 20:58:36 +0800 [thread overview]
Message-ID: <202303131258.32DCwalS871461@localhost.localdomain> (raw)
In-Reply-To: <20230313130428.2650232-1-vfialko@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125070
_Compilation OK_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Mon, 13 Mar 2023 14:04:28 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: baf13c3135d0c5998fff7edc23fb89412dc89246
125070 --> 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
next parent reply other threads:[~2023-03-13 13:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230313130428.2650232-1-vfialko@marvell.com>
2023-03-13 12:58 ` qemudev [this message]
2023-03-13 13:02 ` qemudev
2023-03-13 13:05 ` checkpatch
2023-03-13 15:19 ` 0-day Robot
2023-03-13 16:19 |SUCCESS| pw125070 [PATCH] [v2] " dpdklab
2023-03-13 16:30 dpdklab
2023-03-13 16:38 dpdklab
2023-03-13 16:40 dpdklab
2023-03-13 16:45 dpdklab
2023-03-13 16:48 dpdklab
2023-03-13 16:50 dpdklab
2023-03-13 17:03 dpdklab
2023-03-13 17:04 dpdklab
2023-03-13 17:16 dpdklab
2023-03-13 17:20 dpdklab
2023-03-13 17:26 dpdklab
2023-03-13 17:37 dpdklab
2023-03-13 17:37 dpdklab
2023-03-13 17:38 dpdklab
2023-03-13 18:45 dpdklab
2023-03-14 6:25 dpdklab
2023-03-14 6:34 dpdklab
2023-03-14 6:46 dpdklab
2023-03-14 6:48 dpdklab
2023-03-14 6:57 dpdklab
2023-03-14 7:05 dpdklab
2023-03-14 7:20 dpdklab
2023-03-14 7:24 dpdklab
2023-03-14 7:25 dpdklab
2023-03-14 7:25 dpdklab
2023-03-14 7:38 dpdklab
2023-03-14 7:47 dpdklab
2023-03-14 7:47 dpdklab
2023-03-15 4:55 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=202303131258.32DCwalS871461@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).