From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122851-122859 [PATCH v5 9/9] vhost: enable lock check
Date: Thu, 2 Feb 2023 11:21:52 +0800 [thread overview]
Message-ID: <202302020321.3123LqZY2756913@localhost.localdomain> (raw)
In-Reply-To: <20230201111411.1509520-10-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122859
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Wed, 1 Feb 2023 12:14:03 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 99cc0a9ab6730d4df70dba4b19e78e87ad7ba110
122851-122859 --> 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 prev parent reply other threads:[~2023-02-02 3:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230201111411.1509520-10-david.marchand@redhat.com>
2023-02-01 11:17 ` |SUCCESS| pw122859 " checkpatch
2023-02-01 12:59 ` 0-day Robot
2023-02-02 3:21 ` qemudev [this message]
2023-02-02 3:22 ` |SUCCESS| pw122851-122859 " qemudev
2023-02-02 18:20 |SUCCESS| pw122851-122859 [PATCH] [v5,9/9] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-02 16:00 dpdklab
2023-02-02 15:53 dpdklab
2023-02-02 2:26 dpdklab
2023-02-02 2:26 dpdklab
2023-02-02 2:22 dpdklab
2023-02-02 2:22 dpdklab
2023-02-02 2:22 dpdklab
2023-02-02 2:22 dpdklab
2023-02-02 2:22 dpdklab
2023-02-02 2:22 dpdklab
2023-02-02 2:21 dpdklab
2023-02-02 0:47 dpdklab
2023-02-01 16:24 dpdklab
2023-02-01 14:55 dpdklab
2023-02-01 14:48 dpdklab
2023-02-01 14:44 dpdklab
2023-02-01 14:37 dpdklab
2023-02-01 14:21 dpdklab
2023-02-01 14:19 dpdklab
2023-02-01 14:17 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=202302020321.3123LqZY2756913@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).