From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw134103 [PATCH] net/iavf: fix error devargs parsing
Date: Fri, 10 Nov 2023 18:12:07 +0800 [thread overview]
Message-ID: <202311101012.3AAAC7iP432713@localhost.localdomain> (raw)
In-Reply-To: <20231110102015.469031-1-mingjinx.ye@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/134103
_Compilation OK_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Fri, 10 Nov 2023 10:20:15 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: adeacf1d6f4d96e83857d6f445500d866f958863
134103 --> 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-11-10 10:33 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231110102015.469031-1-mingjinx.ye@intel.com>
2023-11-10 10:12 ` qemudev [this message]
2023-11-10 10:16 ` qemudev
2023-11-10 10:32 ` checkpatch
2023-11-10 11:39 ` 0-day Robot
2023-11-10 14:58 dpdklab
2023-11-10 15:12 dpdklab
2023-11-10 15:15 dpdklab
2023-11-10 15:16 dpdklab
2023-11-10 15:16 dpdklab
2023-11-10 15:19 dpdklab
2023-11-10 15:19 dpdklab
2023-11-10 15:21 dpdklab
2023-11-10 15:37 dpdklab
2023-11-10 15:47 dpdklab
2023-11-10 16:28 dpdklab
2023-11-10 16:28 dpdklab
2023-11-10 16:28 dpdklab
2023-11-10 16:29 dpdklab
2023-11-10 16:29 dpdklab
2023-11-10 16:29 dpdklab
2023-11-10 16:29 dpdklab
2023-11-10 16:29 dpdklab
2023-11-10 16:30 dpdklab
2023-11-10 16:30 dpdklab
2023-11-10 16:30 dpdklab
2023-11-10 16:30 dpdklab
2023-11-10 16:30 dpdklab
2023-11-10 16:38 dpdklab
2023-11-10 16:38 dpdklab
2023-11-10 16:43 dpdklab
2023-11-10 16:43 dpdklab
2023-11-10 16:44 dpdklab
2023-11-10 16:44 dpdklab
2023-11-10 16:45 dpdklab
2023-11-10 16:45 dpdklab
2023-11-10 16:45 dpdklab
2023-11-10 16:45 dpdklab
2023-11-10 16:46 dpdklab
2023-11-10 16:46 dpdklab
2023-11-10 16:46 dpdklab
2023-11-10 16:47 dpdklab
2023-11-10 16:47 dpdklab
2023-11-10 16:50 dpdklab
2023-11-10 16:50 dpdklab
2023-11-10 16:50 dpdklab
2023-11-10 16:51 dpdklab
2023-11-10 16:51 dpdklab
2023-11-10 16:51 dpdklab
2023-11-10 16:52 dpdklab
2023-11-10 16:52 dpdklab
2023-11-10 16:52 dpdklab
2023-11-10 16:53 dpdklab
2023-11-10 16:54 dpdklab
2023-11-10 17:33 dpdklab
2023-11-10 18:14 dpdklab
2023-11-10 19:10 dpdklab
2023-11-10 22:44 dpdklab
2023-11-14 18:11 dpdklab
2023-11-14 18:29 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=202311101012.3AAAC7iP432713@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).