From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125226 [PATCH] net/iavf: fix handle VF reset
Date: Fri, 17 Mar 2023 17:40:17 +0800 [thread overview]
Message-ID: <202303170940.32H9eHJL1214004@localhost.localdomain> (raw)
In-Reply-To: <20230317095506.757964-1-zhichaox.zeng@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125226
_Compilation OK_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Fri, 17 Mar 2023 17:55:06 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 62e4a24aa77b267f765cf16b631e4a4ef104e365
125226 --> 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-03-17 9:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230317095506.757964-1-zhichaox.zeng@intel.com>
2023-03-17 9:40 ` qemudev [this message]
2023-03-17 9:44 ` qemudev
2023-03-17 9:51 ` checkpatch
2023-03-17 11:59 ` 0-day Robot
2023-03-20 9:31 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-20 9:30 dpdklab
2023-03-20 9:27 dpdklab
2023-03-20 9:27 dpdklab
2023-03-20 9:21 dpdklab
2023-03-20 9:16 dpdklab
2023-03-20 9:12 dpdklab
2023-03-20 9:11 dpdklab
2023-03-20 9:07 dpdklab
2023-03-20 9:01 dpdklab
2023-03-20 8:51 dpdklab
2023-03-20 6:32 dpdklab
2023-03-19 18:32 dpdklab
2023-03-19 10:42 dpdklab
2023-03-17 15:23 dpdklab
2023-03-17 12:40 dpdklab
2023-03-17 12:30 dpdklab
2023-03-17 11:15 dpdklab
2023-03-17 11:10 dpdklab
2023-03-17 11:05 dpdklab
2023-03-17 11:00 dpdklab
2023-03-17 10:57 dpdklab
2023-03-17 10:56 dpdklab
2023-03-17 10:56 dpdklab
2023-03-17 10:56 dpdklab
2023-03-17 10:55 dpdklab
2023-03-17 10:50 dpdklab
2023-03-17 10:43 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=202303170940.32H9eHJL1214004@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).