From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139644 [RFC] ethdev: add VXLAN last reserved field
Date: Wed, 24 Apr 2024 10:47:31 +0800 [thread overview]
Message-ID: <202404240247.43O2lVBE1198963@localhost.localdomain> (raw)
In-Reply-To: <20240424031319.1264509-1-rongweil@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139644
_Compilation OK_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Wed, 24 Apr 2024 06:13:19 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 8841786ab4aa72d205f97528af8708a13a851f4f
139644 --> 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:[~2024-04-24 3:15 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240424031319.1264509-1-rongweil@nvidia.com>
2024-04-24 2:47 ` qemudev [this message]
2024-04-24 2:52 ` qemudev
2024-04-24 3:14 ` checkpatch
2024-04-24 3:56 ` |SUCCESS| pw139644 [PATCH] [RFC] ethdev: add VXLAN last reserved fie dpdklab
2024-04-24 3:56 ` dpdklab
2024-04-24 3:57 ` dpdklab
2024-04-24 3:57 ` dpdklab
2024-04-24 3:57 ` dpdklab
2024-04-24 3:57 ` dpdklab
2024-04-24 3:58 ` dpdklab
2024-04-24 3:58 ` dpdklab
2024-04-24 3:58 ` dpdklab
2024-04-24 3:59 ` dpdklab
2024-04-24 3:59 ` dpdklab
2024-04-24 3:59 ` dpdklab
2024-04-24 4:00 ` dpdklab
2024-04-24 4:00 ` dpdklab
2024-04-24 4:00 ` dpdklab
2024-04-24 4:01 ` dpdklab
2024-04-24 4:01 ` dpdklab
2024-04-24 4:02 ` dpdklab
2024-04-24 4:02 ` dpdklab
2024-04-24 4:03 ` dpdklab
2024-04-24 4:04 ` |SUCCESS| pw139644 [RFC] ethdev: add VXLAN last reserved field 0-day Robot
2024-04-24 4:09 ` |SUCCESS| pw139644 [PATCH] [RFC] ethdev: add VXLAN last reserved fie dpdklab
2024-04-24 4:12 ` dpdklab
2024-04-24 4:12 ` dpdklab
2024-04-24 4:17 ` dpdklab
2024-04-24 4:17 ` dpdklab
2024-04-24 4:23 ` dpdklab
2024-04-24 4:23 ` dpdklab
2024-04-24 4:23 ` dpdklab
2024-04-24 4:23 ` dpdklab
2024-04-24 4:24 ` dpdklab
2024-04-24 4:24 ` dpdklab
2024-04-24 4:24 ` dpdklab
2024-04-24 4:24 ` dpdklab
2024-04-24 4:24 ` dpdklab
2024-04-24 4:24 ` dpdklab
2024-04-24 4:24 ` dpdklab
2024-04-24 4:25 ` dpdklab
2024-04-24 4:25 ` dpdklab
2024-04-24 4:25 ` dpdklab
2024-04-24 4:25 ` dpdklab
2024-04-24 4:25 ` dpdklab
2024-04-24 4:25 ` dpdklab
2024-04-24 4:26 ` dpdklab
2024-04-24 4:26 ` dpdklab
2024-04-24 4:26 ` dpdklab
2024-04-24 4:26 ` dpdklab
2024-04-24 4:26 ` dpdklab
2024-04-24 4:26 ` dpdklab
2024-04-24 4:27 ` dpdklab
2024-04-24 4:29 ` dpdklab
2024-04-24 4:29 ` dpdklab
2024-04-24 4:29 ` dpdklab
2024-04-24 4:30 ` dpdklab
2024-04-24 4:30 ` dpdklab
2024-04-24 4:37 ` dpdklab
2024-04-24 4:38 ` dpdklab
2024-04-24 4:39 ` dpdklab
2024-04-24 4:39 ` dpdklab
2024-04-24 4:39 ` dpdklab
2024-04-24 4:39 ` dpdklab
2024-04-24 4:46 ` dpdklab
2024-04-24 4:46 ` dpdklab
2024-04-24 4:46 ` dpdklab
2024-04-24 4:47 ` dpdklab
2024-04-24 4:47 ` dpdklab
2024-04-24 4:55 ` dpdklab
2024-04-24 4:56 ` dpdklab
2024-04-24 5:08 ` dpdklab
2024-04-24 5:08 ` dpdklab
2024-04-24 5:10 ` dpdklab
2024-04-24 5:11 ` dpdklab
2024-04-24 5:11 ` dpdklab
2024-04-24 5:14 ` dpdklab
2024-04-24 5:17 ` dpdklab
2024-04-24 5:19 ` dpdklab
2024-04-24 5:31 ` dpdklab
2024-04-24 5:31 ` dpdklab
2024-04-24 5:32 ` dpdklab
2024-04-24 5:32 ` dpdklab
2024-04-24 5:33 ` dpdklab
2024-04-24 5:37 ` dpdklab
2024-04-24 5:40 ` dpdklab
2024-04-24 5:42 ` dpdklab
2024-04-24 5:44 ` dpdklab
2024-04-24 5:55 ` dpdklab
2024-04-24 6:17 ` dpdklab
2024-04-24 6:27 ` 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=202404240247.43O2lVBE1198963@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).