From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142172 [PATCH] net/mlx5: fix IPv6-in-IPv6 tunnel recognition
Date: Sun, 7 Jul 2024 17:47:12 +0800 [thread overview]
Message-ID: <202407070947.4679lC6C1867471@localhost.localdomain> (raw)
In-Reply-To: <20240707101342.49823-1-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/142172
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Sun, 7 Jul 2024 13:13:41 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: b31811d96c1d0fb36df78dc34ef8325bce447bfc
142172 --> 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-07-07 10:15 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240707101342.49823-1-getelson@nvidia.com>
2024-07-07 9:47 ` qemudev [this message]
2024-07-07 9:51 ` qemudev
2024-07-07 10:15 ` checkpatch
2024-07-07 11:03 ` 0-day Robot
2024-07-08 4:26 ` |SUCCESS| pw142172 [PATCH] net/mlx5: fix IPv6-in-IPv6 tunnel recogni dpdklab
2024-07-08 4:30 ` dpdklab
2024-07-08 4:34 ` dpdklab
2024-07-08 4:37 ` |PENDING| " dpdklab
2024-07-08 4:42 ` |SUCCESS| " dpdklab
2024-07-08 4:48 ` dpdklab
2024-07-08 4:49 ` dpdklab
2024-07-08 4:56 ` dpdklab
2024-07-08 4:59 ` |PENDING| " dpdklab
2024-07-08 5:01 ` dpdklab
2024-07-08 5:01 ` |SUCCESS| " dpdklab
2024-07-08 5:02 ` |PENDING| " dpdklab
2024-07-08 5:04 ` dpdklab
2024-07-08 5:05 ` dpdklab
2024-07-08 5:07 ` |SUCCESS| " dpdklab
2024-07-08 5:13 ` dpdklab
2024-07-08 5:19 ` |PENDING| " dpdklab
2024-07-08 5:20 ` |SUCCESS| " dpdklab
2024-07-08 5:21 ` |PENDING| " dpdklab
2024-07-08 5:23 ` dpdklab
2024-07-08 5:26 ` dpdklab
2024-07-08 5:29 ` dpdklab
2024-07-08 5:30 ` |SUCCESS| " dpdklab
2024-07-08 5:30 ` |PENDING| " dpdklab
2024-07-08 5:43 ` dpdklab
2024-07-08 5:49 ` dpdklab
2024-07-08 5:49 ` dpdklab
2024-07-08 5:55 ` dpdklab
2024-07-08 5:56 ` dpdklab
2024-07-08 5:59 ` dpdklab
2024-07-08 5:59 ` dpdklab
2024-07-08 6:00 ` dpdklab
2024-07-08 6:00 ` dpdklab
2024-07-08 6:01 ` dpdklab
2024-07-08 6:01 ` dpdklab
2024-07-08 6:04 ` dpdklab
2024-07-08 6:06 ` dpdklab
2024-07-08 6:09 ` |SUCCESS| " dpdklab
2024-07-08 6:13 ` dpdklab
2024-07-08 6:30 ` dpdklab
2024-07-08 6:34 ` |PENDING| " dpdklab
2024-07-08 6:36 ` dpdklab
2024-07-08 6:38 ` dpdklab
2024-07-08 6:41 ` dpdklab
2024-07-08 6:41 ` dpdklab
2024-07-08 6:43 ` dpdklab
2024-07-08 6:44 ` dpdklab
2024-07-08 6:46 ` dpdklab
2024-07-08 6:47 ` dpdklab
2024-07-08 6:51 ` dpdklab
2024-07-08 6:54 ` dpdklab
2024-07-08 6:54 ` dpdklab
2024-07-08 6:56 ` dpdklab
2024-07-08 6:56 ` dpdklab
2024-07-08 6:58 ` dpdklab
2024-07-08 6:58 ` dpdklab
2024-07-08 7:02 ` dpdklab
2024-07-08 7:05 ` dpdklab
2024-07-08 7:09 ` dpdklab
2024-07-08 7:11 ` dpdklab
2024-07-08 7:12 ` dpdklab
2024-07-08 7:12 ` dpdklab
2024-07-08 7:13 ` dpdklab
2024-07-08 7:13 ` dpdklab
2024-07-08 7:15 ` dpdklab
2024-07-08 7:16 ` dpdklab
2024-07-08 7:16 ` dpdklab
2024-07-08 7:17 ` dpdklab
2024-07-08 7:17 ` dpdklab
2024-07-08 7:18 ` dpdklab
2024-07-08 7:20 ` dpdklab
2024-07-08 7:23 ` dpdklab
2024-07-08 7:32 ` dpdklab
2024-07-08 7:40 ` dpdklab
2024-07-08 7:45 ` dpdklab
2024-07-08 7:55 ` dpdklab
2024-07-08 8:11 ` dpdklab
2024-07-08 8:32 ` |SUCCESS| " dpdklab
2024-07-08 9:16 ` dpdklab
2024-07-08 9:20 ` dpdklab
2024-07-09 12:05 ` dpdklab
2024-07-09 12:18 ` dpdklab
2024-07-13 23:06 ` dpdklab
2024-07-14 10:51 ` dpdklab
2024-07-14 17:26 ` dpdklab
2024-07-15 10:03 ` dpdklab
2024-07-15 10:10 ` 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=202407070947.4679lC6C1867471@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).