From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw132361 [PATCH v2] net/netvsc: add support for mtu_set
Date: Sat, 7 Oct 2023 03:50:50 +0800 [thread overview]
Message-ID: <202310061950.396JooVm655433@localhost.localdomain> (raw)
In-Reply-To: <MN0PR21MB312032657144AC028C9F0D58B5C9A@MN0PR21MB3120.namprd21.prod.outlook.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/132361
_Compilation OK_
Submitter: Sam Andrew <samandrew@microsoft.com>
Date: Fri, 6 Oct 2023 20:09:09 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 40435075a790fac6e5d5ad7a967950f5e56e45c8
132361 --> 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-10-06 20:11 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MN0PR21MB312032657144AC028C9F0D58B5C9A@MN0PR21MB3120.namprd21.prod.outlook.com>
2023-10-06 19:50 ` qemudev [this message]
2023-10-06 19:55 ` qemudev
2023-10-06 20:10 ` checkpatch
2023-10-06 21:19 ` 0-day Robot
2023-10-06 20:51 |SUCCESS| pw132361 [PATCH] [v2] " dpdklab
2023-10-06 20:51 dpdklab
2023-10-06 20:52 dpdklab
2023-10-06 20:52 dpdklab
2023-10-06 20:53 dpdklab
2023-10-06 20:53 dpdklab
2023-10-06 20:54 dpdklab
2023-10-06 20:55 dpdklab
2023-10-06 20:57 dpdklab
2023-10-06 20:57 dpdklab
2023-10-06 20:58 dpdklab
2023-10-06 20:58 dpdklab
2023-10-06 20:59 dpdklab
2023-10-06 20:59 dpdklab
2023-10-06 20:59 dpdklab
2023-10-06 21:00 dpdklab
2023-10-06 21:03 dpdklab
2023-10-06 21:04 dpdklab
2023-10-06 21:04 dpdklab
2023-10-06 21:05 dpdklab
2023-10-06 21:05 dpdklab
2023-10-06 21:06 dpdklab
2023-10-06 21:07 dpdklab
2023-10-06 21:17 dpdklab
2023-10-06 21:18 dpdklab
2023-10-06 21:27 dpdklab
2023-10-06 21:27 dpdklab
2023-10-06 21:29 dpdklab
2023-10-06 21:30 dpdklab
2023-10-06 21:30 dpdklab
2023-10-06 21:32 dpdklab
2023-10-06 21:33 dpdklab
2023-10-06 21:35 dpdklab
2023-10-06 21:38 dpdklab
2023-10-06 21:51 dpdklab
2023-10-06 21:52 dpdklab
2023-10-06 21:54 dpdklab
2023-10-06 22:06 dpdklab
2023-10-06 22:06 dpdklab
2023-10-06 22:07 dpdklab
2023-10-06 22:20 dpdklab
2023-10-06 22:31 dpdklab
2023-10-06 22:34 dpdklab
2023-10-06 22:35 dpdklab
2023-10-06 22:36 dpdklab
2023-10-06 22:41 dpdklab
2023-10-06 22:42 dpdklab
2023-10-06 22:43 dpdklab
2023-10-06 22:44 dpdklab
2023-10-06 22:44 dpdklab
2023-10-06 22:44 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=202310061950.396JooVm655433@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).