From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135193 [PATCH v2] net/iavf: fix no polling mode switch
Date: Thu, 14 Dec 2023 18:30:22 +0800 [thread overview]
Message-ID: <202312141030.3BEAUMZm822227@localhost.localdomain> (raw)
In-Reply-To: <20231214103302.900680-1-mingjinx.ye@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/135193
_Compilation OK_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Thu, 14 Dec 2023 10:33:02 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 2e68ed42cde16c71264201e3e1affdc3b0f8d0bd
135193 --> 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-12-14 10:51 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231214103302.900680-1-mingjinx.ye@intel.com>
2023-12-14 10:30 ` qemudev [this message]
2023-12-14 10:34 ` qemudev
2023-12-14 10:50 ` |WARNING| " checkpatch
2023-12-14 11:44 ` |SUCCESS| " 0-day Robot
2023-12-14 17:39 |SUCCESS| pw135193 [PATCH] [v2] " dpdklab
2023-12-14 17:46 dpdklab
2023-12-14 17:49 dpdklab
2023-12-14 17:50 dpdklab
2023-12-14 17:50 dpdklab
2023-12-14 17:51 dpdklab
2023-12-14 17:52 dpdklab
2023-12-14 17:53 dpdklab
2023-12-14 17:58 dpdklab
2023-12-14 17:58 dpdklab
2023-12-14 18:00 dpdklab
2023-12-14 18:00 dpdklab
2023-12-14 18:01 dpdklab
2023-12-14 18:05 dpdklab
2023-12-14 18:07 dpdklab
2023-12-14 18:38 dpdklab
2023-12-14 18:39 dpdklab
2023-12-14 18:40 dpdklab
2023-12-14 18:47 dpdklab
2023-12-14 18:48 dpdklab
2023-12-14 18:49 dpdklab
2023-12-14 18:49 dpdklab
2023-12-14 18:50 dpdklab
2023-12-14 18:51 dpdklab
2023-12-14 18:52 dpdklab
2023-12-14 18:52 dpdklab
2023-12-14 18:52 dpdklab
2023-12-14 18:53 dpdklab
2023-12-14 18:53 dpdklab
2023-12-14 18:53 dpdklab
2023-12-14 18:54 dpdklab
2023-12-14 18:59 dpdklab
2023-12-14 19:04 dpdklab
2023-12-14 19:09 dpdklab
2023-12-14 19:11 dpdklab
2023-12-14 19:24 dpdklab
2023-12-14 19:24 dpdklab
2023-12-14 19:25 dpdklab
2023-12-14 19:25 dpdklab
2023-12-14 19:26 dpdklab
2023-12-14 19:28 dpdklab
2023-12-14 19:30 dpdklab
2023-12-14 19:31 dpdklab
2023-12-14 19:37 dpdklab
2023-12-14 19:39 dpdklab
2023-12-14 19:39 dpdklab
2023-12-14 19:40 dpdklab
2023-12-14 19:40 dpdklab
2023-12-14 19:43 dpdklab
2023-12-14 19:46 dpdklab
2023-12-14 19:48 dpdklab
2023-12-14 19:50 dpdklab
2023-12-14 19:57 dpdklab
2023-12-14 19:57 dpdklab
2023-12-14 19:58 dpdklab
2023-12-14 19:59 dpdklab
2023-12-14 20:00 dpdklab
2023-12-14 20:15 dpdklab
2023-12-14 20:20 dpdklab
2023-12-14 20:21 dpdklab
2023-12-14 20:21 dpdklab
2023-12-14 20:27 dpdklab
2023-12-14 20:27 dpdklab
2023-12-14 20:29 dpdklab
2023-12-15 1: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=202312141030.3BEAUMZm822227@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).