From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123286-123279 [PATCH v2 21/21] net/virtio-user: remove max queues limitation
Date: Tue, 7 Feb 2023 23:23:55 +0800 [thread overview]
Message-ID: <202302071523.317FNtl2858172@localhost.localdomain> (raw)
In-Reply-To: <20230207151747.245808-22-maxime.coquelin@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123279
_Compilation OK_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Tue, 7 Feb 2023 16:17:27 +0100
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: fe2c18a0a8b22703dec3add385a371ad819d7872
123286-123279 --> 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 15:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230207151747.245808-22-maxime.coquelin@redhat.com>
2023-02-07 15:22 ` |SUCCESS| pw123279 " checkpatch
2023-02-07 15:23 ` qemudev [this message]
2023-02-07 15:27 ` |SUCCESS| pw123286-123279 " qemudev
2023-02-07 18:39 ` |SUCCESS| pw123279 " 0-day Robot
2023-02-07 16:06 |SUCCESS| pw123286-123279 [PATCH] [v2, " dpdklab
2023-02-07 16:14 dpdklab
2023-02-07 16:17 dpdklab
2023-02-07 16:21 dpdklab
2023-02-07 16:26 dpdklab
2023-02-07 16:32 dpdklab
2023-02-07 16:36 dpdklab
2023-02-07 16:38 dpdklab
2023-02-07 16:50 dpdklab
2023-02-07 17:03 dpdklab
2023-02-07 20:14 dpdklab
2023-02-08 11:25 dpdklab
2023-02-08 12:10 dpdklab
2023-02-08 12:58 dpdklab
2023-02-08 12:59 dpdklab
2023-02-08 12:59 dpdklab
2023-02-08 13:00 dpdklab
2023-02-08 13:00 dpdklab
2023-02-08 23:59 dpdklab
2023-02-09 4:10 dpdklab
2023-02-09 13:23 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=202302071523.317FNtl2858172@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).