From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139181 [PATCH] net/mlx5/hws: add fragment packet ID matching support
Date: Mon, 8 Apr 2024 14:10:29 +0800 [thread overview]
Message-ID: <202404080610.4386ATHO3671188@localhost.localdomain> (raw)
In-Reply-To: <20240408063210.2600860-1-michaelba@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139181
_Compilation OK_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Mon, 8 Apr 2024 09:32:10 +0300
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
139181 --> 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-04-08 6:35 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240408063210.2600860-1-michaelba@nvidia.com>
2024-04-08 6:10 ` qemudev [this message]
2024-04-08 6:14 ` qemudev
2024-04-08 6:33 ` checkpatch
2024-04-08 7:24 ` 0-day Robot
2024-04-08 7:51 ` |SUCCESS| pw139181 [PATCH] net/mlx5/hws: add fragment packet ID matc dpdklab
2024-04-08 7:55 ` dpdklab
2024-04-08 7:55 ` dpdklab
2024-04-08 7:57 ` dpdklab
2024-04-08 8:33 ` dpdklab
2024-04-08 8:35 ` dpdklab
2024-04-08 8:36 ` dpdklab
2024-04-08 8:37 ` dpdklab
2024-04-08 8:38 ` dpdklab
2024-04-08 8:39 ` dpdklab
2024-04-08 8:40 ` dpdklab
2024-04-08 8:40 ` dpdklab
2024-04-08 8:40 ` dpdklab
2024-04-08 8:40 ` dpdklab
2024-04-08 8:41 ` dpdklab
2024-04-08 8:41 ` dpdklab
2024-04-08 8:41 ` dpdklab
2024-04-08 8:41 ` dpdklab
2024-04-08 8:42 ` dpdklab
2024-04-08 8:42 ` dpdklab
2024-04-08 8:42 ` dpdklab
2024-04-08 8:42 ` dpdklab
2024-04-08 8:42 ` dpdklab
2024-04-08 8:42 ` dpdklab
2024-04-08 8:43 ` dpdklab
2024-04-08 8:43 ` dpdklab
2024-04-08 8:43 ` dpdklab
2024-04-08 8:43 ` dpdklab
2024-04-08 8:44 ` dpdklab
2024-04-08 8:44 ` dpdklab
2024-04-08 8:44 ` dpdklab
2024-04-08 8:45 ` dpdklab
2024-04-08 8:45 ` dpdklab
2024-04-08 8:45 ` dpdklab
2024-04-08 8:46 ` dpdklab
2024-04-08 8:46 ` dpdklab
2024-04-08 8:46 ` dpdklab
2024-04-08 8:47 ` dpdklab
2024-04-08 8:47 ` dpdklab
2024-04-08 8:47 ` dpdklab
2024-04-08 8:47 ` dpdklab
2024-04-08 8:47 ` dpdklab
2024-04-08 8:47 ` dpdklab
2024-04-08 8:48 ` dpdklab
2024-04-08 8:48 ` dpdklab
2024-04-08 8:48 ` dpdklab
2024-04-08 8:48 ` dpdklab
2024-04-08 8:48 ` dpdklab
2024-04-08 8:49 ` dpdklab
2024-04-08 8:49 ` dpdklab
2024-04-08 8:49 ` dpdklab
2024-04-08 8:49 ` dpdklab
2024-04-08 8:50 ` dpdklab
2024-04-08 8:50 ` dpdklab
2024-04-08 8:50 ` dpdklab
2024-04-08 8:50 ` dpdklab
2024-04-08 8:50 ` dpdklab
2024-04-08 8:51 ` dpdklab
2024-04-08 8:51 ` dpdklab
2024-04-08 8:51 ` dpdklab
2024-04-08 8:51 ` dpdklab
2024-04-08 8:51 ` dpdklab
2024-04-08 8:52 ` dpdklab
2024-04-08 8:52 ` dpdklab
2024-04-08 8:52 ` dpdklab
2024-04-08 8:52 ` dpdklab
2024-04-08 8:52 ` dpdklab
2024-04-08 8:52 ` dpdklab
2024-04-08 8:53 ` dpdklab
2024-04-08 8:53 ` dpdklab
2024-04-08 8:53 ` dpdklab
2024-04-08 8:53 ` dpdklab
2024-04-08 8:54 ` dpdklab
2024-04-08 8:54 ` dpdklab
2024-04-08 8:54 ` dpdklab
2024-04-08 8:54 ` dpdklab
2024-04-08 8:55 ` dpdklab
2024-04-08 8:56 ` |FAILURE| " dpdklab
2024-04-08 9:07 ` |SUCCESS| " dpdklab
2024-04-08 9:10 ` dpdklab
2024-04-08 9:18 ` dpdklab
2024-04-08 9:29 ` dpdklab
2024-04-08 9:30 ` dpdklab
2024-04-08 9:31 ` dpdklab
2024-04-08 9:39 ` dpdklab
2024-04-08 9:43 ` 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=202404080610.4386ATHO3671188@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).