From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133867 [PATCH] net/bnxt: fix deadlock in mgr timer cb
Date: Sat, 4 Nov 2023 11:59:43 +0800 [thread overview]
Message-ID: <202311040359.3A43xhq64160896@localhost.localdomain> (raw)
In-Reply-To: <tencent_7B6D2301220A31DB3CA9A701112E3A47DF08@qq.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133867
_Compilation OK_
Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Sat, 4 Nov 2023 12:06:58 +0800
DPDK git baseline: Repo:dpdk-next-net-brcm
Branch: for-next-net
CommitID: ecca8a0be606f4bbdeee1e76bdce16c3e1ff4d89
133867 --> 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:20 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_7B6D2301220A31DB3CA9A701112E3A47DF08@qq.com>
2023-11-04 3:59 ` qemudev [this message]
2023-11-04 4:03 ` qemudev
2023-11-04 4:07 ` |WARNING| " checkpatch
2023-11-04 5:19 ` |SUCCESS| " 0-day Robot
2023-11-04 5:30 dpdklab
2023-11-04 5:32 dpdklab
2023-11-04 5:32 dpdklab
2023-11-04 5:35 dpdklab
2023-11-04 5:35 dpdklab
2023-11-04 5:36 dpdklab
2023-11-04 5:37 dpdklab
2023-11-04 5:38 dpdklab
2023-11-04 5:38 dpdklab
2023-11-04 5:39 dpdklab
2023-11-04 5:39 dpdklab
2023-11-04 5:40 dpdklab
2023-11-04 5:42 dpdklab
2023-11-04 5:49 dpdklab
2023-11-04 5:49 dpdklab
2023-11-04 5:55 dpdklab
2023-11-04 5:55 dpdklab
2023-11-04 5:55 dpdklab
2023-11-04 5:59 dpdklab
2023-11-04 6:10 dpdklab
2023-11-04 6:29 dpdklab
2023-11-04 7:55 dpdklab
2023-11-04 7:55 dpdklab
2023-11-04 7:55 dpdklab
2023-11-04 7:56 dpdklab
2023-11-04 8:01 dpdklab
2023-11-04 8:17 dpdklab
2023-11-04 8:25 dpdklab
2023-11-04 8:37 dpdklab
2023-11-04 8:47 dpdklab
2023-11-04 8:48 dpdklab
2023-11-04 8:49 dpdklab
2023-11-04 8:50 dpdklab
2023-11-04 8:50 dpdklab
2023-11-04 8:51 dpdklab
2023-11-04 8:51 dpdklab
2023-11-04 8:52 dpdklab
2023-11-04 8:52 dpdklab
2023-11-04 8:52 dpdklab
2023-11-04 8:53 dpdklab
2023-11-04 8:57 dpdklab
2023-11-04 8:58 dpdklab
2023-11-04 9:01 dpdklab
2023-11-04 9:02 dpdklab
2023-11-04 9:02 dpdklab
2023-11-04 9:02 dpdklab
2023-11-04 9:02 dpdklab
2023-11-04 9:03 dpdklab
2023-11-04 9:03 dpdklab
2023-11-04 9:04 dpdklab
2023-11-04 9:07 dpdklab
2023-11-04 9:09 dpdklab
2023-11-04 10:58 dpdklab
2023-11-04 11:01 dpdklab
2023-11-06 15:26 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=202311040359.3A43xhq64160896@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).