From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126609-126615 [PATCH v3 next 7/7] net/vmxnet3: update to version 7
Date: Fri, 28 Apr 2023 15:17:15 +0800 [thread overview]
Message-ID: <202304280717.33S7HFd52853619@localhost.localdomain> (raw)
In-Reply-To: <20230428071055.362-8-doshir@vmware.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126615
_Compilation OK_
Submitter: Ronak Doshi <doshir@vmware.com>
Date: Fri, 28 Apr 2023 00:10:48 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: b6367469a9368234bc5ed931dc9ba29474e7d347
126609-126615 --> 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-04-28 7:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230428071055.362-8-doshir@vmware.com>
2023-04-28 7:17 ` qemudev [this message]
2023-04-28 7:21 ` qemudev
2023-04-28 7:29 ` |SUCCESS| pw126615 " checkpatch
2023-04-28 8:59 ` 0-day Robot
2023-04-28 7:50 |SUCCESS| pw126609-126615 [PATCH] [v3, next, " dpdklab
2023-04-28 7:53 dpdklab
2023-04-28 7:58 dpdklab
2023-04-28 7:59 dpdklab
2023-04-28 8:05 dpdklab
2023-04-28 8:06 dpdklab
2023-04-28 8:09 dpdklab
2023-04-28 8:18 dpdklab
2023-04-28 8:19 dpdklab
2023-04-28 8:23 dpdklab
2023-04-28 8:24 dpdklab
2023-04-28 8:24 dpdklab
2023-04-28 8:24 dpdklab
2023-04-28 8:25 dpdklab
2023-04-28 8:27 dpdklab
2023-04-28 8:30 dpdklab
2023-04-28 8:30 dpdklab
2023-04-28 8:31 dpdklab
2023-04-28 8:37 dpdklab
2023-04-28 8:37 dpdklab
2023-04-28 8:48 dpdklab
2023-04-28 14:54 dpdklab
2023-04-28 20:22 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=202304280717.33S7HFd52853619@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).