From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw136945 [PATCH] net/mlx5: fix condition of LACP miss flow
Date: Wed, 21 Feb 2024 14:27:22 +0800 [thread overview]
Message-ID: <202402210627.41L6RMZ83428729@localhost.localdomain> (raw)
In-Reply-To: <20240221064948.298863-1-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/136945
_Compilation OK_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Wed, 21 Feb 2024 08:49:48 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: ee45c93a16dd5e11b7779f18db9173fd8de8df74
136945 --> 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-21 6:52 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240221064948.298863-1-bingz@nvidia.com>
2024-02-21 6:27 ` qemudev [this message]
2024-02-21 6:31 ` qemudev
2024-02-21 6:51 ` |WARNING| " checkpatch
2024-02-21 7:44 ` |SUCCESS| " 0-day Robot
2024-02-21 9:10 dpdklab
2024-02-21 9:10 dpdklab
2024-02-21 9:11 dpdklab
2024-02-21 9:12 dpdklab
2024-02-21 9:12 dpdklab
2024-02-21 9:12 dpdklab
2024-02-21 9:13 dpdklab
2024-02-21 9:13 dpdklab
2024-02-21 9:14 dpdklab
2024-02-21 9:14 dpdklab
2024-02-21 9:15 dpdklab
2024-02-21 9:15 dpdklab
2024-02-21 9:15 dpdklab
2024-02-21 9:16 dpdklab
2024-02-21 9:17 dpdklab
2024-02-21 9:17 dpdklab
2024-02-21 9:18 dpdklab
2024-02-21 9:18 dpdklab
2024-02-21 9:18 dpdklab
2024-02-21 9:19 dpdklab
2024-02-21 9:19 dpdklab
2024-02-21 9:20 dpdklab
2024-02-21 9:20 dpdklab
2024-02-21 9:20 dpdklab
2024-02-21 9:20 dpdklab
2024-02-21 9:20 dpdklab
2024-02-21 9:21 dpdklab
2024-02-21 9:21 dpdklab
2024-02-21 9:21 dpdklab
2024-02-21 9:22 dpdklab
2024-02-21 9:22 dpdklab
2024-02-21 9:22 dpdklab
2024-02-21 9:22 dpdklab
2024-02-21 9:22 dpdklab
2024-02-21 9:23 dpdklab
2024-02-21 9:23 dpdklab
2024-02-21 9:23 dpdklab
2024-02-21 9:23 dpdklab
2024-02-21 9:23 dpdklab
2024-02-21 9:24 dpdklab
2024-02-21 9:24 dpdklab
2024-02-21 9:24 dpdklab
2024-02-21 9:25 dpdklab
2024-02-21 9:25 dpdklab
2024-02-21 9:25 dpdklab
2024-02-21 9:25 dpdklab
2024-02-21 9:25 dpdklab
2024-02-21 9:26 dpdklab
2024-02-21 9:26 dpdklab
2024-02-21 9:26 dpdklab
2024-02-21 9:26 dpdklab
2024-02-21 9:26 dpdklab
2024-02-21 9:27 dpdklab
2024-02-21 9:27 dpdklab
2024-02-21 9:27 dpdklab
2024-02-21 9:27 dpdklab
2024-02-21 9:28 dpdklab
2024-02-21 9:47 dpdklab
2024-02-21 10:02 dpdklab
2024-02-21 10:09 dpdklab
2024-02-21 10:20 dpdklab
2024-02-21 15:54 dpdklab
2024-02-21 15:55 dpdklab
2024-02-21 17:11 dpdklab
2024-02-21 17:45 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=202402210627.41L6RMZ83428729@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).