From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123796 [PATCH] eal/bsd: fix spinlock not unlock in alarm callback
Date: Mon, 13 Feb 2023 20:39:56 +0800 [thread overview]
Message-ID: <202302131239.31DCdu113179216@localhost.localdomain> (raw)
In-Reply-To: <20230213124452.46536-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123796
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Mon, 13 Feb 2023 12:44:52 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 39d469a7eb4f157923be73aea0b0cc1015860ca7
123796 --> 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-02-13 12:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230213124452.46536-1-fengchengwen@huawei.com>
2023-02-13 12:39 ` qemudev [this message]
2023-02-13 12:43 ` qemudev
2023-02-13 12:52 ` checkpatch
2023-02-14 0:39 ` 0-day Robot
2023-02-15 15:12 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-14 23:22 dpdklab
2023-02-14 21:04 dpdklab
2023-02-13 22:10 dpdklab
2023-02-13 22:10 dpdklab
2023-02-13 22:03 dpdklab
2023-02-13 22:00 dpdklab
2023-02-13 21:58 dpdklab
2023-02-13 21:53 dpdklab
2023-02-13 21:43 dpdklab
2023-02-13 21:41 dpdklab
2023-02-13 21:35 dpdklab
2023-02-13 21:27 dpdklab
2023-02-13 21:22 dpdklab
2023-02-13 21:15 dpdklab
2023-02-13 21:05 dpdklab
2023-02-13 14:59 dpdklab
2023-02-13 13:48 dpdklab
2023-02-13 13:41 dpdklab
2023-02-13 13:37 dpdklab
2023-02-13 13:35 dpdklab
2023-02-13 13:34 dpdklab
2023-02-13 13:33 dpdklab
2023-02-13 13:30 dpdklab
2023-02-13 13:28 dpdklab
2023-02-13 13:22 dpdklab
2023-02-13 13:17 dpdklab
2023-02-13 13:15 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=202302131239.31DCdu113179216@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).