From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137508-137509 [PATCH 2/2] net/mlx5: fix IP-in-IP tunnels recognition
Date: Thu, 29 Feb 2024 23:43:55 +0800 [thread overview]
Message-ID: <202402291543.41TFhtaP2451113@localhost.localdomain> (raw)
In-Reply-To: <20240229160505.630586-3-getelson@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137509
_Compilation OK_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thu, 29 Feb 2024 18:05:03 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 387aefe9fab8f1033071659a758ccda61a220ffd
137508-137509 --> 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-02-29 16:08 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229160505.630586-3-getelson@nvidia.com>
2024-02-29 15:43 ` qemudev [this message]
2024-02-29 15:48 ` qemudev
2024-02-29 16:06 ` |SUCCESS| pw137509 " checkpatch
2024-02-29 17:05 ` 0-day Robot
2024-02-29 18:34 ` |SUCCESS| pw137508-137509 [PATCH] [2/2] net/mlx5: fix IP-in-IP tunne dpdklab
2024-02-29 18:56 ` dpdklab
2024-02-29 18:58 ` dpdklab
2024-02-29 18:59 ` dpdklab
2024-02-29 19:03 ` dpdklab
2024-02-29 19:04 ` dpdklab
2024-02-29 19:06 ` dpdklab
2024-02-29 19:07 ` dpdklab
2024-02-29 19:20 ` dpdklab
2024-02-29 19:24 ` dpdklab
2024-02-29 19:24 ` dpdklab
2024-02-29 19:24 ` dpdklab
2024-02-29 19:25 ` dpdklab
2024-02-29 19:35 ` dpdklab
2024-02-29 19:36 ` dpdklab
2024-02-29 20:04 ` dpdklab
2024-02-29 20:36 ` dpdklab
2024-02-29 20:59 ` dpdklab
2024-02-29 21:03 ` dpdklab
2024-02-29 21:03 ` dpdklab
2024-02-29 21:06 ` dpdklab
2024-02-29 21:07 ` dpdklab
2024-02-29 21:08 ` dpdklab
2024-02-29 21:12 ` dpdklab
2024-02-29 21:13 ` dpdklab
2024-02-29 21:14 ` dpdklab
2024-02-29 21:14 ` dpdklab
2024-02-29 21:14 ` dpdklab
2024-02-29 21:15 ` dpdklab
2024-02-29 21:15 ` dpdklab
2024-02-29 21:15 ` dpdklab
2024-02-29 21:16 ` dpdklab
2024-02-29 21:16 ` dpdklab
2024-02-29 21:16 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:17 ` dpdklab
2024-02-29 21:18 ` dpdklab
2024-02-29 21:18 ` dpdklab
2024-02-29 21:19 ` dpdklab
2024-02-29 21:22 ` dpdklab
2024-02-29 21:23 ` dpdklab
2024-02-29 21:26 ` dpdklab
2024-02-29 21:26 ` dpdklab
2024-02-29 21:33 ` dpdklab
2024-02-29 21:33 ` dpdklab
2024-02-29 21:33 ` dpdklab
2024-02-29 21:34 ` dpdklab
2024-02-29 21:35 ` dpdklab
2024-02-29 21:35 ` dpdklab
2024-02-29 21:37 ` dpdklab
2024-02-29 21:38 ` dpdklab
2024-02-29 21:41 ` dpdklab
2024-02-29 21:46 ` dpdklab
2024-02-29 21:47 ` dpdklab
2024-02-29 21:50 ` dpdklab
2024-02-29 21:51 ` dpdklab
2024-02-29 22:13 ` dpdklab
2024-02-29 22:18 ` dpdklab
2024-02-29 23:58 ` dpdklab
2024-03-01 5:08 ` dpdklab
2024-03-01 9:14 ` dpdklab
2024-03-01 9:20 ` dpdklab
2024-03-01 9:25 ` dpdklab
2024-03-01 9:30 ` dpdklab
2024-03-02 9:28 ` dpdklab
2024-03-03 12:52 ` dpdklab
2024-03-03 13:25 ` dpdklab
2024-03-03 13:57 ` 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=202402291543.41TFhtaP2451113@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).