From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133868 [PATCH] net/mlx5: fix the unlock mismatch issue
Date: Sat, 4 Nov 2023 11:54:25 +0800 [thread overview]
Message-ID: <202311040354.3A43sP1W4108516@localhost.localdomain> (raw)
In-Reply-To: <tencent_D1651EC7D3B588081DFD6FF1112691E61807@qq.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133868
_Compilation OK_
Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Sat, 4 Nov 2023 12:07:33 +0800
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: ee70470b08ce3abf13849b310cfdac84b4eae1d2
133868 --> 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-11-04 4:15 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_D1651EC7D3B588081DFD6FF1112691E61807@qq.com>
2023-11-04 3:54 ` qemudev [this message]
2023-11-04 3:58 ` qemudev
2023-11-04 4:09 ` |WARNING| " checkpatch
2023-11-04 5:19 ` |SUCCESS| " 0-day Robot
2023-11-04 9:17 dpdklab
2023-11-04 9:42 dpdklab
2023-11-04 9:43 dpdklab
2023-11-04 9:43 dpdklab
2023-11-04 9:44 dpdklab
2023-11-04 9:54 dpdklab
2023-11-04 9:54 dpdklab
2023-11-04 10:03 dpdklab
2023-11-04 10:04 dpdklab
2023-11-04 10:05 dpdklab
2023-11-04 10:05 dpdklab
2023-11-04 10:06 dpdklab
2023-11-04 10:06 dpdklab
2023-11-04 10:06 dpdklab
2023-11-04 10:06 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:07 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:08 dpdklab
2023-11-04 10:09 dpdklab
2023-11-04 10:09 dpdklab
2023-11-04 10:09 dpdklab
2023-11-04 10:09 dpdklab
2023-11-04 10:10 dpdklab
2023-11-04 10:10 dpdklab
2023-11-04 10:10 dpdklab
2023-11-04 10:10 dpdklab
2023-11-04 10:11 dpdklab
2023-11-04 10:11 dpdklab
2023-11-04 10:13 dpdklab
2023-11-04 10:13 dpdklab
2023-11-04 10:14 dpdklab
2023-11-04 10:15 dpdklab
2023-11-04 10:15 dpdklab
2023-11-04 10:16 dpdklab
2023-11-04 10:19 dpdklab
2023-11-04 10:22 dpdklab
2023-11-04 10:22 dpdklab
2023-11-04 10:22 dpdklab
2023-11-04 10:22 dpdklab
2023-11-04 10:22 dpdklab
2023-11-04 10:25 dpdklab
2023-11-04 11:04 dpdklab
2023-11-04 11:24 dpdklab
2023-11-04 12:47 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=202311040354.3A43sP1W4108516@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).