From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124437 [PATCH v2] vhost: fix madvise arguments alignment
Date: Thu, 23 Feb 2023 12:24:47 +0800 [thread overview]
Message-ID: <202302230424.31N4OlP52703135@localhost.localdomain> (raw)
In-Reply-To: <20230223043551.1108541-1-mkp@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124437
_Compilation OK_
Submitter: Mike Pattrick <mkp@redhat.com>
Date: Wed, 22 Feb 2023 23:35:51 -0500
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7710b5d15a014872a3aaf646668dafa928ca8473
124437 --> 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-23 4:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230223043551.1108541-1-mkp@redhat.com>
2023-02-23 4:24 ` qemudev [this message]
2023-02-23 4:28 ` qemudev
2023-02-23 4:37 ` checkpatch
2023-02-23 6:59 ` |FAILURE| " 0-day Robot
2023-02-23 11:11 |SUCCESS| pw124437 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 8:03 dpdklab
2023-02-23 8:03 dpdklab
2023-02-23 8:01 dpdklab
2023-02-23 7:59 dpdklab
2023-02-23 7:45 dpdklab
2023-02-23 7:43 dpdklab
2023-02-23 7:40 dpdklab
2023-02-23 7:39 dpdklab
2023-02-23 7:37 dpdklab
2023-02-23 7:35 dpdklab
2023-02-23 7:33 dpdklab
2023-02-23 7:23 dpdklab
2023-02-23 7:07 dpdklab
2023-02-23 5:23 dpdklab
2023-02-23 5:18 dpdklab
2023-02-23 5:15 dpdklab
2023-02-23 5:14 dpdklab
2023-02-23 5:11 dpdklab
2023-02-23 5:09 dpdklab
2023-02-23 5:03 dpdklab
2023-02-23 5:03 dpdklab
2023-02-23 5:02 dpdklab
2023-02-23 4:58 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=202302230424.31N4OlP52703135@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).