From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw152374-152375 [PATCH 2/2] net/mlx5: fix GENEVE parser cleanup
Date: Thu, 13 Mar 2025 16:01:17 +0800 [thread overview]
Message-ID: <202503130801.52D81H70482127@localhost.localdomain> (raw)
In-Reply-To: <20250313083351.25559-2-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/152375
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thu, 13 Mar 2025 10:33:50 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 3d88504a3bb4d2022d4d55b099829d6dd0a97723
152374-152375 --> 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:[~2025-03-13 8:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250313083351.25559-2-getelson@nvidia.com>
2025-03-13 8:01 ` qemudev [this message]
2025-03-13 8:05 ` qemudev
2025-03-13 8:35 ` |SUCCESS| pw152375 " checkpatch
2025-03-13 10:02 ` 0-day Robot
2025-03-13 10:47 ` |SUCCESS| pw152374-152375 [PATCH] [2/2] net/mlx5: fix GENEVE parser dpdklab
2025-03-13 10:55 ` dpdklab
2025-03-13 10:57 ` dpdklab
2025-03-13 11:09 ` dpdklab
2025-03-13 11:11 ` dpdklab
2025-03-13 11:17 ` dpdklab
2025-03-13 11:19 ` dpdklab
2025-03-13 11:20 ` dpdklab
2025-03-13 11:33 ` dpdklab
2025-03-13 11:36 ` dpdklab
2025-03-13 12:19 ` |PENDING| " dpdklab
2025-03-13 12:42 ` dpdklab
2025-03-13 13:04 ` |SUCCESS| " dpdklab
2025-03-13 13:13 ` dpdklab
2025-03-13 13:20 ` dpdklab
2025-03-13 14:06 ` dpdklab
2025-03-13 14:09 ` dpdklab
2025-03-13 15:08 ` dpdklab
2025-03-13 15:14 ` dpdklab
2025-03-13 15:42 ` dpdklab
2025-03-13 15:45 ` dpdklab
2025-03-13 16: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=202503130801.52D81H70482127@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).