automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw132354 [PATCH] net/netvsc: add support for mtu_set
Date: Fri, 6 Oct 2023 06:58:09 +0800	[thread overview]
Message-ID: <202310052258.395Mw91m303735@localhost.localdomain> (raw)
In-Reply-To: <MN0PR21MB3120FDA48E7C122E74FF58F0B5CAA@MN0PR21MB3120.namprd21.prod.outlook.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/132354

_Compilation OK_

Submitter: Sam Andrew <samandrew@microsoft.com>
Date: Thu, 5 Oct 2023 23:17:28 +0000
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 40435075a790fac6e5d5ad7a967950f5e56e45c8

132354 --> 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


       reply	other threads:[~2023-10-05 23:19 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MN0PR21MB3120FDA48E7C122E74FF58F0B5CAA@MN0PR21MB3120.namprd21.prod.outlook.com>
2023-10-05 22:58 ` qemudev [this message]
2023-10-05 23:02 ` qemudev
2023-10-05 23:17 ` |WARNING| " checkpatch
2023-10-06  0:19 ` |SUCCESS| " 0-day Robot
2023-10-06  3:50 dpdklab
2023-10-06  3:51 dpdklab
2023-10-06  3:53 dpdklab
2023-10-06  3:53 dpdklab
2023-10-06  3:53 dpdklab
2023-10-06  3:54 dpdklab
2023-10-06  3:54 dpdklab
2023-10-06  3:56 dpdklab
2023-10-06  3:58 dpdklab
2023-10-06  3:58 dpdklab
2023-10-06  3:59 dpdklab
2023-10-06  4:00 dpdklab
2023-10-06  4:01 dpdklab
2023-10-06  4:01 dpdklab
2023-10-06  4:02 dpdklab
2023-10-06  4:02 dpdklab
2023-10-06  4:03 dpdklab
2023-10-06  4:05 dpdklab
2023-10-06  4:06 dpdklab
2023-10-06  4:06 dpdklab
2023-10-06  4:06 dpdklab
2023-10-06  4:07 dpdklab
2023-10-06  4:07 dpdklab
2023-10-06  4:07 dpdklab
2023-10-06  4:07 dpdklab
2023-10-06  4:07 dpdklab
2023-10-06  4:08 dpdklab
2023-10-06  4:08 dpdklab
2023-10-06  4:08 dpdklab
2023-10-06  4:08 dpdklab
2023-10-06  4:09 dpdklab
2023-10-06  4:09 dpdklab
2023-10-06  4:09 dpdklab
2023-10-06  4:09 dpdklab
2023-10-06  4:09 dpdklab
2023-10-06  4:18 dpdklab
2023-10-06  4:21 dpdklab
2023-10-06  4:26 dpdklab
2023-10-06  4:28 dpdklab
2023-10-06  4:41 dpdklab
2023-10-06  4:41 dpdklab
2023-10-06  4:41 dpdklab
2023-10-06  4:43 dpdklab
2023-10-06  4:43 dpdklab
2023-10-06  4:45 dpdklab
2023-10-06  4:46 dpdklab
2023-10-06  4:55 dpdklab
2023-10-06  5: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=202310052258.395Mw91m303735@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).