From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info in version.map
Date: Fri, 15 Mar 2024 00:16:56 +0800 [thread overview]
Message-ID: <202403141616.42EGGu2U1260152@localhost.localdomain> (raw)
In-Reply-To: <20240314162819.16971-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138406
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 14 Mar 2024 09:28:19 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: cd218549b686d6be394ef3b171eafa16c038bfe3
138406 --> 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-14 16:41 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314162819.16971-1-stephen@networkplumber.org>
2024-03-14 16:16 ` qemudev [this message]
2024-03-14 16:21 ` qemudev
2024-03-14 16:28 ` checkpatch
2024-03-14 17:11 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info i dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:13 ` dpdklab
2024-03-14 17:13 ` dpdklab
2024-03-14 17:13 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:15 ` dpdklab
2024-03-14 17:16 ` dpdklab
2024-03-14 17:19 ` dpdklab
2024-03-14 17:20 ` dpdklab
2024-03-14 17:20 ` dpdklab
2024-03-14 17:20 ` dpdklab
2024-03-14 17:21 ` dpdklab
2024-03-14 17:21 ` dpdklab
2024-03-14 17:21 ` dpdklab
2024-03-14 17:21 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:23 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info in version.map 0-day Robot
2024-03-14 17:24 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info i dpdklab
2024-03-14 17:24 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:26 ` dpdklab
2024-03-14 17:26 ` dpdklab
2024-03-14 17:26 ` dpdklab
2024-03-14 17:27 ` dpdklab
2024-03-14 17:27 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:32 ` dpdklab
2024-03-14 17:33 ` dpdklab
2024-03-14 17:33 ` dpdklab
2024-03-14 17:36 ` dpdklab
2024-03-14 17:36 ` dpdklab
2024-03-14 17:36 ` dpdklab
2024-03-14 17:56 ` dpdklab
2024-03-14 18:30 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:51 ` 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=202403141616.42EGGu2U1260152@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).