From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139626 [PATCH v3] net/vmxnet3: fix a missing vmxnet3 register command
Date: Tue, 23 Apr 2024 01:45:21 +0800 [thread overview]
Message-ID: <202404221745.43MHjLcf741746@localhost.localdomain> (raw)
In-Reply-To: <20240422181050.9661-1-ronak.doshi@broadcom.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139626
_Compilation OK_
Submitter: Ronak Doshi <ronak.doshi@broadcom.com>
Date: Mon, 22 Apr 2024 11:10:50 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 8841786ab4aa72d205f97528af8708a13a851f4f
139626 --> 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-04-22 18:13 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240422181050.9661-1-ronak.doshi@broadcom.com>
2024-04-22 17:45 ` qemudev [this message]
2024-04-22 17:49 ` qemudev
2024-04-22 18:12 ` |WARNING| " checkpatch
2024-04-22 19:00 ` |SUCCESS| pw139626 [PATCH] [v3] net/vmxnet3: fix a missing vmxnet3 r dpdklab
2024-04-22 19:01 ` dpdklab
2024-04-22 19:04 ` |SUCCESS| pw139626 [PATCH v3] net/vmxnet3: fix a missing vmxnet3 register command 0-day Robot
2024-04-22 19:07 ` |SUCCESS| pw139626 [PATCH] [v3] net/vmxnet3: fix a missing vmxnet3 r dpdklab
2024-04-22 19:07 ` dpdklab
2024-04-22 19:08 ` dpdklab
2024-04-22 19:08 ` dpdklab
2024-04-22 19:08 ` dpdklab
2024-04-22 19:09 ` dpdklab
2024-04-22 19:09 ` dpdklab
2024-04-22 19:09 ` dpdklab
2024-04-22 19:10 ` dpdklab
2024-04-22 19:10 ` dpdklab
2024-04-22 19:10 ` dpdklab
2024-04-22 19:11 ` dpdklab
2024-04-22 19:11 ` dpdklab
2024-04-22 19:12 ` dpdklab
2024-04-22 19:13 ` dpdklab
2024-04-22 19:15 ` dpdklab
2024-04-22 19:16 ` dpdklab
2024-04-22 19:16 ` dpdklab
2024-04-22 19:16 ` dpdklab
2024-04-22 19:17 ` dpdklab
2024-04-22 19:17 ` dpdklab
2024-04-22 19:18 ` dpdklab
2024-04-22 19:18 ` dpdklab
2024-04-22 19:19 ` dpdklab
2024-04-22 19:20 ` dpdklab
2024-04-22 19:24 ` dpdklab
2024-04-22 19:25 ` dpdklab
2024-04-22 19:26 ` dpdklab
2024-04-22 19:26 ` dpdklab
2024-04-22 19:27 ` dpdklab
2024-04-22 19:28 ` dpdklab
2024-04-22 19:28 ` dpdklab
2024-04-22 19:29 ` dpdklab
2024-04-22 19:29 ` dpdklab
2024-04-22 19:32 ` dpdklab
2024-04-22 19:32 ` dpdklab
2024-04-22 19:32 ` dpdklab
2024-04-22 19:42 ` dpdklab
2024-04-22 19:42 ` dpdklab
2024-04-22 19:42 ` dpdklab
2024-04-22 19:42 ` dpdklab
2024-04-22 19:42 ` dpdklab
2024-04-22 19:44 ` dpdklab
2024-04-22 19:46 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:48 ` dpdklab
2024-04-22 19:50 ` dpdklab
2024-04-22 19:53 ` dpdklab
2024-04-22 19:54 ` dpdklab
2024-04-22 19:54 ` dpdklab
2024-04-22 19:54 ` dpdklab
2024-04-22 19:55 ` dpdklab
2024-04-22 19:56 ` dpdklab
2024-04-22 19:57 ` dpdklab
2024-04-22 20:00 ` dpdklab
2024-04-22 20:00 ` dpdklab
2024-04-22 20:00 ` dpdklab
2024-04-22 20:01 ` dpdklab
2024-04-22 20:01 ` dpdklab
2024-04-22 20:01 ` dpdklab
2024-04-22 20:01 ` dpdklab
2024-04-22 20:02 ` dpdklab
2024-04-22 20:04 ` dpdklab
2024-04-22 20:04 ` dpdklab
2024-04-22 20:04 ` dpdklab
2024-04-22 20:06 ` dpdklab
2024-04-22 20:07 ` dpdklab
2024-04-22 20:07 ` dpdklab
2024-04-22 20:07 ` dpdklab
2024-04-22 20:19 ` dpdklab
2024-04-22 20:36 ` dpdklab
2024-04-22 20:39 ` dpdklab
2024-04-22 20:47 ` dpdklab
2024-04-22 20:47 ` dpdklab
2024-04-22 20:48 ` dpdklab
2024-04-22 20:52 ` dpdklab
2024-04-22 20:58 ` dpdklab
2024-04-22 21:00 ` dpdklab
2024-04-22 21:03 ` dpdklab
2024-04-22 21:05 ` dpdklab
2024-04-22 21:40 ` 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=202404221745.43MHjLcf741746@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).