From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135877 [PATCH] net/mlx5/hws: fix ESP matching validation
Date: Mon, 15 Jan 2024 19:48:23 +0800 [thread overview]
Message-ID: <202401151148.40FBmNdt917130@localhost.localdomain> (raw)
In-Reply-To: <20240115120938.3994588-1-michaelba@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/135877
_Compilation OK_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Mon, 15 Jan 2024 14:09:39 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 30468d404a3447cae8797576e885b9831bb88391
135877 --> 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-01-15 12:13 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240115120938.3994588-1-michaelba@nvidia.com>
2024-01-15 11:48 ` qemudev [this message]
2024-01-15 11:52 ` qemudev
2024-01-15 12:10 ` checkpatch
2024-01-15 12:43 ` 0-day Robot
2024-01-15 13:16 dpdklab
2024-01-15 13:19 dpdklab
2024-01-15 13:21 dpdklab
2024-01-15 13:21 dpdklab
2024-01-15 13:30 dpdklab
2024-01-15 13:37 dpdklab
2024-01-15 13:39 dpdklab
2024-01-15 13:39 dpdklab
2024-01-15 13:40 dpdklab
2024-01-15 13:41 dpdklab
2024-01-15 13:42 dpdklab
2024-01-15 13:42 dpdklab
2024-01-15 13:43 dpdklab
2024-01-15 13:44 dpdklab
2024-01-15 13:45 dpdklab
2024-01-15 13:46 dpdklab
2024-01-15 13:46 dpdklab
2024-01-15 13:46 dpdklab
2024-01-15 13:47 dpdklab
2024-01-15 13:47 dpdklab
2024-01-15 13:47 dpdklab
2024-01-15 13:48 dpdklab
2024-01-15 13:49 dpdklab
2024-01-15 13:49 dpdklab
2024-01-15 13:49 dpdklab
2024-01-15 13:50 dpdklab
2024-01-15 13:50 dpdklab
2024-01-15 13:51 dpdklab
2024-01-15 13:51 dpdklab
2024-01-15 13:51 dpdklab
2024-01-15 13:52 dpdklab
2024-01-15 13:52 dpdklab
2024-01-15 13:52 dpdklab
2024-01-15 13:52 dpdklab
2024-01-15 13:53 dpdklab
2024-01-15 13:53 dpdklab
2024-01-15 13:53 dpdklab
2024-01-15 13:53 dpdklab
2024-01-15 13:57 dpdklab
2024-01-15 13:58 dpdklab
2024-01-15 14:01 dpdklab
2024-01-15 14:02 dpdklab
2024-01-15 14:03 dpdklab
2024-01-15 14:06 dpdklab
2024-01-15 14:07 dpdklab
2024-01-15 14:08 dpdklab
2024-01-15 14:08 dpdklab
2024-01-15 14:11 dpdklab
2024-01-15 14:12 dpdklab
2024-01-15 14:13 dpdklab
2024-01-15 14:13 dpdklab
2024-01-15 14:13 dpdklab
2024-01-15 14:14 dpdklab
2024-01-15 14:15 dpdklab
2024-01-15 14:15 dpdklab
2024-01-15 14:16 dpdklab
2024-01-15 14:17 dpdklab
2024-01-15 14:19 dpdklab
2024-01-15 14:20 dpdklab
2024-01-15 14:20 dpdklab
2024-01-15 14:21 dpdklab
2024-01-15 14:22 dpdklab
2024-01-15 14:23 dpdklab
2024-01-15 14:26 dpdklab
2024-01-15 14:26 dpdklab
2024-01-15 14:28 dpdklab
2024-01-15 14:32 dpdklab
2024-01-15 14:42 dpdklab
2024-01-15 14:55 dpdklab
2024-01-15 14:55 dpdklab
2024-01-16 18:51 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=202401151148.40FBmNdt917130@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).