From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138129 [PATCH v2] net/netvsc: fix number Tx queues > Rx queues
Date: Sat, 9 Mar 2024 02:04:56 +0800 [thread overview]
Message-ID: <202403081804.428I4uk81404846@localhost.localdomain> (raw)
In-Reply-To: <DU0PR83MB05321DB2ADBEDAE7687773DF97272@DU0PR83MB0532.EURPRD83.prod.outlook.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138129
_Compilation OK_
Submitter: Alan Elder <alan.elder@microsoft.com>
Date: Fri, 8 Mar 2024 18:09:53 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: a86f381b826660e88794754c41d3aec79ce9b87c
138129 --> 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-08 18:29 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DU0PR83MB05321DB2ADBEDAE7687773DF97272@DU0PR83MB0532.EURPRD83.prod.outlook.com>
2024-03-08 18:04 ` qemudev [this message]
2024-03-08 18:09 ` qemudev
2024-03-08 18:10 ` checkpatch
2024-03-08 18:44 ` |SUCCESS| pw138129 [PATCH] [v2] net/netvsc: fix number Tx queues > R dpdklab
2024-03-08 18:45 ` dpdklab
2024-03-08 18:45 ` dpdklab
2024-03-08 18:46 ` dpdklab
2024-03-08 18:46 ` dpdklab
2024-03-08 18:46 ` dpdklab
2024-03-08 18:46 ` dpdklab
2024-03-08 18:47 ` dpdklab
2024-03-08 18:47 ` dpdklab
2024-03-08 18:48 ` dpdklab
2024-03-08 18:48 ` dpdklab
2024-03-08 18:48 ` dpdklab
2024-03-08 18:49 ` dpdklab
2024-03-08 18:49 ` dpdklab
2024-03-08 18:49 ` dpdklab
2024-03-08 18:49 ` dpdklab
2024-03-08 18:50 ` dpdklab
2024-03-08 18:50 ` dpdklab
2024-03-08 18:51 ` dpdklab
2024-03-08 18:51 ` dpdklab
2024-03-08 18:52 ` dpdklab
2024-03-08 18:52 ` dpdklab
2024-03-08 18:52 ` dpdklab
2024-03-08 18:53 ` dpdklab
2024-03-08 18:53 ` dpdklab
2024-03-08 18:53 ` dpdklab
2024-03-08 18:53 ` dpdklab
2024-03-08 18:53 ` dpdklab
2024-03-08 18:54 ` dpdklab
2024-03-08 18:54 ` dpdklab
2024-03-08 18:54 ` dpdklab
2024-03-08 18:54 ` dpdklab
2024-03-08 18:54 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:59 ` dpdklab
2024-03-08 18:59 ` dpdklab
2024-03-08 19:00 ` dpdklab
2024-03-08 19:02 ` dpdklab
2024-03-08 19:03 ` dpdklab
2024-03-08 19:03 ` |SUCCESS| pw138129 [PATCH v2] net/netvsc: fix number Tx queues > Rx queues 0-day Robot
2024-03-08 19:04 ` |SUCCESS| pw138129 [PATCH] [v2] net/netvsc: fix number Tx queues > R dpdklab
2024-03-08 19:07 ` dpdklab
2024-03-08 19:14 ` dpdklab
2024-03-08 19:27 ` dpdklab
2024-03-08 20:09 ` dpdklab
2024-03-13 10:37 ` dpdklab
2024-03-13 11:00 ` 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=202403081804.428I4uk81404846@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).