From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140184 [PATCH] net/mlx5/hws: add support for NVGRE matching
Date: Mon, 20 May 2024 14:04:28 +0800 [thread overview]
Message-ID: <202405200604.44K64SiZ180848@localhost.localdomain> (raw)
In-Reply-To: <20240520062524.2401676-1-dongzhou@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140184
_Compilation OK_
Submitter: Dong Zhou <dongzhou@nvidia.com>
Date: Mon, 20 May 2024 09:25:24 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: a7699c5af857f57eec072cd19ceb1b03998ffe57
140184 --> 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-05-20 6:33 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240520062524.2401676-1-dongzhou@nvidia.com>
2024-05-20 6:04 ` qemudev [this message]
2024-05-20 6:09 ` qemudev
2024-05-20 6:26 ` |WARNING| " checkpatch
2024-05-20 7:24 ` |SUCCESS| " 0-day Robot
2024-05-20 16:48 ` |SUCCESS| pw140184 [PATCH] net/mlx5/hws: add support for NVGRE match dpdklab
2024-05-20 16:50 ` dpdklab
2024-05-20 16:52 ` dpdklab
2024-05-20 16:52 ` dpdklab
2024-05-20 16:59 ` dpdklab
2024-05-20 17:30 ` dpdklab
2024-05-20 17:34 ` dpdklab
2024-05-20 17:34 ` dpdklab
2024-05-20 17:36 ` dpdklab
2024-05-20 17:37 ` dpdklab
2024-05-20 17:38 ` dpdklab
2024-05-20 17:38 ` dpdklab
2024-05-20 17:39 ` dpdklab
2024-05-20 17:39 ` dpdklab
2024-05-20 17:39 ` dpdklab
2024-05-20 17:39 ` dpdklab
2024-05-20 17:39 ` dpdklab
2024-05-20 17:40 ` dpdklab
2024-05-20 17:40 ` dpdklab
2024-05-20 17:40 ` |FAILURE| " dpdklab
2024-05-20 17:41 ` dpdklab
2024-05-20 17:41 ` dpdklab
2024-05-20 17:41 ` |SUCCESS| " dpdklab
2024-05-20 17:41 ` dpdklab
2024-05-20 17:41 ` dpdklab
2024-05-20 17:41 ` dpdklab
2024-05-20 17:42 ` dpdklab
2024-05-20 17:42 ` |FAILURE| " dpdklab
2024-05-20 17:42 ` |SUCCESS| " dpdklab
2024-05-20 17:42 ` dpdklab
2024-05-20 17:42 ` dpdklab
2024-05-20 17:42 ` dpdklab
2024-05-20 17:43 ` |FAILURE| " dpdklab
2024-05-20 17:43 ` dpdklab
2024-05-20 17:43 ` |SUCCESS| " dpdklab
2024-05-20 17:43 ` dpdklab
2024-05-20 17:44 ` dpdklab
2024-05-20 17:44 ` dpdklab
2024-05-20 17:44 ` dpdklab
2024-05-20 17:44 ` dpdklab
2024-05-20 17:45 ` |FAILURE| " dpdklab
2024-05-20 17:45 ` |SUCCESS| " dpdklab
2024-05-20 17:45 ` dpdklab
2024-05-20 17:45 ` |FAILURE| " dpdklab
2024-05-20 17:46 ` dpdklab
2024-05-20 17:46 ` |SUCCESS| " dpdklab
2024-05-20 17:46 ` dpdklab
2024-05-20 17:46 ` |FAILURE| " dpdklab
2024-05-20 17:47 ` |SUCCESS| " dpdklab
2024-05-20 17:47 ` dpdklab
2024-05-20 17:47 ` dpdklab
2024-05-20 17:47 ` dpdklab
2024-05-20 17:47 ` dpdklab
2024-05-20 17:47 ` |FAILURE| " dpdklab
2024-05-20 17:47 ` |SUCCESS| " dpdklab
2024-05-20 17:47 ` dpdklab
2024-05-20 17:47 ` dpdklab
2024-05-20 17:48 ` dpdklab
2024-05-20 17:48 ` dpdklab
2024-05-20 17:48 ` dpdklab
2024-05-20 17:48 ` dpdklab
2024-05-20 17:49 ` dpdklab
2024-05-20 17:49 ` |FAILURE| " dpdklab
2024-05-20 17:49 ` |SUCCESS| " dpdklab
2024-05-20 17:49 ` dpdklab
2024-05-20 17:49 ` dpdklab
2024-05-20 17:50 ` dpdklab
2024-05-20 17:50 ` |FAILURE| " dpdklab
2024-05-20 17:50 ` |SUCCESS| " dpdklab
2024-05-20 17:51 ` dpdklab
2024-05-20 17:51 ` |FAILURE| " dpdklab
2024-05-20 17:51 ` dpdklab
2024-05-20 17:56 ` dpdklab
2024-05-20 17:59 ` |SUCCESS| " dpdklab
2024-05-20 18:00 ` dpdklab
2024-05-20 18:01 ` |FAILURE| " dpdklab
2024-05-20 18:03 ` |SUCCESS| " dpdklab
2024-05-20 18:07 ` dpdklab
2024-05-20 18:21 ` dpdklab
2024-05-20 18:45 ` dpdklab
2024-05-20 18:49 ` dpdklab
2024-05-20 20:14 ` dpdklab
2024-05-23 5: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=202405200604.44K64SiZ180848@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).