From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw149048 [PATCH] net/mlx5: do not poll CQEs when no available elts
Date: Fri, 6 Dec 2024 08:47:50 +0800 [thread overview]
Message-ID: <202412060047.4B60lo1D3806548@localhost.localdomain> (raw)
In-Reply-To: <20241206005811.948293-1-gahu@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/149048
_Compilation OK_
Submitter: Gavin Hu <gahu@nvidia.com>
Date: Fri, 6 Dec 2024 02:58:11 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 1b3bf1128d9bda5595861814792f74b8f57160c8
149048 --> 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-12-06 1:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241206005811.948293-1-gahu@nvidia.com>
2024-12-06 0:47 ` qemudev [this message]
2024-12-06 0:52 ` qemudev
2024-12-06 0:59 ` |WARNING| " checkpatch
2024-12-06 1:49 ` |PENDING| pw149048 [PATCH] net/mlx5: do not poll CQEs when no availa dpdklab
2024-12-06 1:50 ` dpdklab
2024-12-06 2:01 ` |SUCCESS| " dpdklab
2024-12-06 2:02 ` dpdklab
2024-12-06 2:05 ` dpdklab
2024-12-06 2:07 ` dpdklab
2024-12-06 2:13 ` dpdklab
2024-12-06 2:22 ` |SUCCESS| pw149048 [PATCH] net/mlx5: do not poll CQEs when no available elts 0-day Robot
2024-12-06 2:55 ` |SUCCESS| pw149048 [PATCH] net/mlx5: do not poll CQEs when no availa dpdklab
2024-12-06 3:51 ` dpdklab
2024-12-06 23:30 ` |PENDING| " dpdklab
2024-12-07 0:59 ` |WARNING| " dpdklab
2024-12-07 2:03 ` dpdklab
2024-12-07 2:40 ` dpdklab
2024-12-07 2:44 ` 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=202412060047.4B60lo1D3806548@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).