From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123214-123222 [PATCH v6 9/9] vhost: enable lock check
Date: Tue, 7 Feb 2023 19:05:01 +0800 [thread overview]
Message-ID: <202302071105.317B51pv520175@localhost.localdomain> (raw)
In-Reply-To: <20230207104532.2370869-10-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123222
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Tue, 7 Feb 2023 11:45:24 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: b29ccbea24ae3a6da4ff3769c4fe702b0702a4b5
123214-123222 --> 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-07 11:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230207104532.2370869-10-david.marchand@redhat.com>
2023-02-07 10:47 ` |SUCCESS| pw123222 " checkpatch
2023-02-07 11:05 ` qemudev [this message]
2023-02-07 11:09 ` |SUCCESS| pw123214-123222 " qemudev
2023-02-07 11:59 ` |SUCCESS| pw123222 " 0-day Robot
2023-02-07 11:09 |SUCCESS| pw123214-123222 [PATCH] [v6,9/9] " dpdklab
2023-02-07 11:11 dpdklab
2023-02-07 11:15 dpdklab
2023-02-07 11:17 dpdklab
2023-02-07 11:18 dpdklab
2023-02-07 11:20 dpdklab
2023-02-07 11:24 dpdklab
2023-02-07 11:24 dpdklab
2023-02-07 11:25 dpdklab
2023-02-07 11:28 dpdklab
2023-02-07 11:32 dpdklab
2023-02-07 15:02 dpdklab
2023-02-08 2:49 dpdklab
2023-02-08 3:25 dpdklab
2023-02-08 3:37 dpdklab
2023-02-08 3:46 dpdklab
2023-02-08 3:46 dpdklab
2023-02-08 3:46 dpdklab
2023-02-08 3:46 dpdklab
2023-02-08 3:46 dpdklab
2023-02-08 3:46 dpdklab
2023-02-08 3:47 dpdklab
2023-02-08 13:32 dpdklab
2023-02-08 17:39 dpdklab
2023-02-09 2:36 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=202302071105.317B51pv520175@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).