From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125457 [PATCH] net/mlx5/hws: fix IPv4 frag matching
Date: Thu, 23 Mar 2023 20:24:35 +0800 [thread overview]
Message-ID: <202303231224.32NCOZ31825795@localhost.localdomain> (raw)
In-Reply-To: <20230323123416.26636-3-valex@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125457
_Compilation OK_
Submitter: Alex Vesker <valex@nvidia.com>
Date: Thu, 23 Mar 2023 14:34:16 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 99e5d9cf55156b80e8a3e26e2a32ec63709a497c
125457 --> 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:[~2023-03-23 12:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230323123416.26636-3-valex@nvidia.com>
2023-03-23 12:24 ` qemudev [this message]
2023-03-23 12:28 ` qemudev
2023-03-23 12:35 ` |WARNING| " checkpatch
2023-03-23 13:59 ` |SUCCESS| " 0-day Robot
2023-03-23 14:29 dpdklab
2023-03-23 14:36 dpdklab
2023-03-23 14:42 dpdklab
2023-03-23 14:46 dpdklab
2023-03-23 14:53 dpdklab
2023-03-23 14:55 dpdklab
2023-03-23 14:56 dpdklab
2023-03-23 14:57 dpdklab
2023-03-23 15:02 dpdklab
2023-03-23 15:08 dpdklab
2023-03-23 15:14 dpdklab
2023-03-23 15:15 dpdklab
2023-03-23 15:16 dpdklab
2023-03-23 15:20 dpdklab
2023-03-23 15:21 dpdklab
2023-03-23 15:24 dpdklab
2023-03-23 15:26 dpdklab
2023-03-23 15:27 dpdklab
2023-03-23 15:33 dpdklab
2023-03-23 15:36 dpdklab
2023-03-23 15:41 dpdklab
2023-03-23 15:43 dpdklab
2023-03-23 15:53 dpdklab
2023-03-23 16:16 dpdklab
2023-03-23 16:56 dpdklab
2023-03-23 17:55 dpdklab
2023-03-24 3:19 dpdklab
2023-03-24 3:31 dpdklab
2023-03-25 13:20 dpdklab
2023-03-25 14:17 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=202303231224.32NCOZ31825795@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).