From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138329-138330 [PATCH v2 2/2] net/virtio: fix notification area initialization
Date: Wed, 13 Mar 2024 20:37:20 +0800 [thread overview]
Message-ID: <202403131237.42DCbKrU117116@localhost.localdomain> (raw)
In-Reply-To: <20240313125932.1878279-3-maxime.coquelin@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138330
_Compilation OK_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Wed, 13 Mar 2024 13:59:31 +0100
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: deedfb86a7a6e10064d3cccd593f62072de96e36
138329-138330 --> 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:[~2024-03-13 13:02 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240313125932.1878279-3-maxime.coquelin@redhat.com>
2024-03-13 12:37 ` qemudev [this message]
2024-03-13 12:41 ` qemudev
2024-03-13 13:01 ` |SUCCESS| pw138330 " checkpatch
2024-03-13 13:34 ` |SUCCESS| pw138329-138330 [PATCH] [v2,2/2] net/virtio: fix notificat dpdklab
2024-03-13 13:34 ` dpdklab
2024-03-13 13:34 ` dpdklab
2024-03-13 13:35 ` dpdklab
2024-03-13 13:35 ` dpdklab
2024-03-13 13:36 ` dpdklab
2024-03-13 13:36 ` dpdklab
2024-03-13 13:37 ` dpdklab
2024-03-13 13:37 ` dpdklab
2024-03-13 13:37 ` dpdklab
2024-03-13 13:38 ` dpdklab
2024-03-13 13:39 ` dpdklab
2024-03-13 13:39 ` dpdklab
2024-03-13 13:39 ` dpdklab
2024-03-13 13:39 ` dpdklab
2024-03-13 13:40 ` dpdklab
2024-03-13 13:40 ` dpdklab
2024-03-13 13:41 ` dpdklab
2024-03-13 13:42 ` dpdklab
2024-03-13 13:42 ` dpdklab
2024-03-13 13:43 ` dpdklab
2024-03-13 13:43 ` dpdklab
2024-03-13 13:43 ` dpdklab
2024-03-13 13:43 ` dpdklab
2024-03-13 13:44 ` dpdklab
2024-03-13 13:44 ` dpdklab
2024-03-13 13:44 ` dpdklab
2024-03-13 13:46 ` dpdklab
2024-03-13 13:46 ` dpdklab
2024-03-13 13:47 ` dpdklab
2024-03-13 13:47 ` dpdklab
2024-03-13 13:47 ` dpdklab
2024-03-13 13:48 ` dpdklab
2024-03-13 13:48 ` dpdklab
2024-03-13 13:48 ` dpdklab
2024-03-13 13:48 ` dpdklab
2024-03-13 13:48 ` dpdklab
2024-03-13 13:49 ` dpdklab
2024-03-13 13:54 ` dpdklab
2024-03-13 13:55 ` dpdklab
2024-03-13 13:56 ` dpdklab
2024-03-13 13:59 ` dpdklab
2024-03-13 13:59 ` dpdklab
2024-03-13 13:59 ` dpdklab
2024-03-13 14:03 ` dpdklab
2024-03-13 14:04 ` |SUCCESS| pw138330 [PATCH v2 2/2] net/virtio: fix notification area initialization 0-day Robot
2024-03-13 14:04 ` |SUCCESS| pw138329-138330 [PATCH] [v2,2/2] net/virtio: fix notificat dpdklab
2024-03-13 14:04 ` dpdklab
2024-03-13 14:05 ` dpdklab
2024-03-13 14:05 ` dpdklab
2024-03-13 14:08 ` dpdklab
2024-03-13 14:08 ` dpdklab
2024-03-13 14:09 ` dpdklab
2024-03-13 14:13 ` dpdklab
2024-03-13 14:19 ` dpdklab
2024-03-13 14:19 ` dpdklab
2024-03-13 14:20 ` dpdklab
2024-03-13 14:21 ` dpdklab
2024-03-13 14:22 ` dpdklab
2024-03-13 14:23 ` dpdklab
2024-03-13 14:25 ` dpdklab
2024-03-13 14:26 ` dpdklab
2024-03-13 14:32 ` dpdklab
2024-03-13 14:34 ` dpdklab
2024-03-13 14:35 ` dpdklab
2024-03-13 14:39 ` dpdklab
2024-03-13 14:40 ` dpdklab
2024-03-13 14:41 ` dpdklab
2024-03-13 14:55 ` dpdklab
2024-03-17 4:00 ` dpdklab
2024-03-17 5:09 ` 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=202403131237.42DCbKrU117116@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).