From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137463 [PATCH] net/mlx5: fix the counters map in bonding mode
Date: Thu, 29 Feb 2024 17:16:25 +0800 [thread overview]
Message-ID: <202402290916.41T9GPrM1669627@localhost.localdomain> (raw)
In-Reply-To: <20240229093456.306768-1-bingz@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137463
_Compilation OK_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Thu, 29 Feb 2024 11:34:56 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 513a698fe1ddcb725d0ed6bca2cbc4b6fc7c8345
137463 --> 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-29 9:41 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229093456.306768-1-bingz@nvidia.com>
2024-02-29 9:16 ` qemudev [this message]
2024-02-29 9:20 ` qemudev
2024-02-29 9:37 ` |WARNING| " checkpatch
2024-02-29 10:24 ` |SUCCESS| " 0-day Robot
2024-02-29 10:29 ` |SUCCESS| pw137463 [PATCH] net/mlx5: fix the counters map in bonding dpdklab
2024-02-29 10:30 ` dpdklab
2024-02-29 10:30 ` dpdklab
2024-02-29 10:30 ` dpdklab
2024-02-29 10:30 ` dpdklab
2024-02-29 10:30 ` dpdklab
2024-02-29 10:31 ` dpdklab
2024-02-29 10:31 ` dpdklab
2024-02-29 10:31 ` dpdklab
2024-02-29 10:31 ` dpdklab
2024-02-29 10:31 ` dpdklab
2024-02-29 10:32 ` dpdklab
2024-02-29 10:32 ` dpdklab
2024-02-29 10:32 ` dpdklab
2024-02-29 10:32 ` dpdklab
2024-02-29 10:32 ` dpdklab
2024-02-29 10:32 ` dpdklab
2024-02-29 10:32 ` dpdklab
2024-02-29 10:33 ` dpdklab
2024-02-29 10:33 ` dpdklab
2024-02-29 10:33 ` dpdklab
2024-02-29 10:33 ` dpdklab
2024-02-29 10:33 ` dpdklab
2024-02-29 10:33 ` dpdklab
2024-02-29 10:33 ` dpdklab
2024-02-29 10:33 ` dpdklab
2024-02-29 10:34 ` dpdklab
2024-02-29 10:34 ` dpdklab
2024-02-29 10:34 ` dpdklab
2024-02-29 10:34 ` dpdklab
2024-02-29 10:34 ` dpdklab
2024-02-29 10:34 ` dpdklab
2024-02-29 10:34 ` dpdklab
2024-02-29 10:35 ` dpdklab
2024-02-29 10:35 ` dpdklab
2024-02-29 10:35 ` dpdklab
2024-02-29 10:35 ` dpdklab
2024-02-29 10:35 ` dpdklab
2024-02-29 10:35 ` dpdklab
2024-02-29 10:35 ` dpdklab
2024-02-29 10:36 ` dpdklab
2024-02-29 10:36 ` dpdklab
2024-02-29 10:36 ` dpdklab
2024-02-29 10:36 ` dpdklab
2024-02-29 10:36 ` dpdklab
2024-02-29 10:36 ` dpdklab
2024-02-29 10:36 ` dpdklab
2024-02-29 10:37 ` dpdklab
2024-02-29 10:37 ` dpdklab
2024-02-29 10:38 ` dpdklab
2024-02-29 10:38 ` dpdklab
2024-02-29 10:39 ` dpdklab
2024-02-29 10:40 ` dpdklab
2024-02-29 10:42 ` dpdklab
2024-02-29 10:42 ` dpdklab
2024-02-29 10:42 ` dpdklab
2024-02-29 10:42 ` dpdklab
2024-02-29 10:45 ` dpdklab
2024-02-29 10:52 ` dpdklab
2024-02-29 10:56 ` dpdklab
2024-02-29 11:06 ` dpdklab
2024-02-29 12:04 ` dpdklab
2024-03-01 4:39 ` dpdklab
2024-03-01 4:46 ` dpdklab
2024-03-01 4:47 ` dpdklab
2024-03-01 4:50 ` dpdklab
2024-03-02 3:41 ` dpdklab
2024-03-02 15:39 ` dpdklab
2024-03-02 16:12 ` dpdklab
2024-03-02 16: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=202402290916.41T9GPrM1669627@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).