From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132470 [PATCH] [v3] net/netvsc: add support for mtu_set
Date: Tue, 10 Oct 2023 21:11:56 -0700 (PDT) [thread overview]
Message-ID: <6526208c.920a0220.4ab29.b3ccSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132470
_Testing PASS_
Submitter: Sam Andrew <samandrew@microsoft.com>
Date: Tuesday, October 10 2023 18:41:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4dd146e597d81d900140a904e0b3b9feb1b0be6c
132470 --> testing pass
Test environment and result as below:
+----------------------+------------------------------+---------------------------+--------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | lpm_autotest |
+======================+==============================+===========================+==============+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+----------------------+------------------------------+---------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | PASS |
+----------------------+------------------------------+---------------------------+--------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27888/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-11 4:11 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 4:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-12 6:20 dpdklab
2023-10-12 5:53 dpdklab
2023-10-12 4:36 dpdklab
2023-10-12 4:34 dpdklab
2023-10-12 4:32 dpdklab
2023-10-11 12:42 dpdklab
2023-10-11 8:22 dpdklab
2023-10-11 6:52 dpdklab
2023-10-11 6:38 dpdklab
2023-10-11 6:23 dpdklab
2023-10-11 5:33 dpdklab
2023-10-11 5:31 dpdklab
2023-10-11 5:22 dpdklab
2023-10-11 4:23 dpdklab
2023-10-11 4:20 dpdklab
2023-10-11 4:20 dpdklab
2023-10-11 4:18 dpdklab
2023-10-11 4:18 dpdklab
2023-10-11 4:17 dpdklab
2023-10-11 4:17 dpdklab
2023-10-11 4:17 dpdklab
2023-10-11 4:15 dpdklab
2023-10-11 4:14 dpdklab
2023-10-11 4:14 dpdklab
2023-10-11 4:13 dpdklab
2023-10-11 4:12 dpdklab
2023-10-11 4:12 dpdklab
2023-10-11 4:12 dpdklab
2023-10-11 4:12 dpdklab
2023-10-11 4:12 dpdklab
2023-10-11 4:09 dpdklab
2023-10-11 4:05 dpdklab
2023-10-11 4:03 dpdklab
2023-10-11 4:03 dpdklab
2023-10-11 4:03 dpdklab
2023-10-11 4:02 dpdklab
2023-10-11 4:01 dpdklab
2023-10-11 4:01 dpdklab
2023-10-11 3:20 dpdklab
2023-10-11 3:20 dpdklab
2023-10-11 3:19 dpdklab
2023-10-10 23:35 dpdklab
2023-10-10 23:27 dpdklab
2023-10-10 22:27 dpdklab
2023-10-10 22:12 dpdklab
2023-10-10 21:23 dpdklab
2023-10-10 21:22 dpdklab
2023-10-10 21:09 dpdklab
[not found] <MN0PR21MB31200B879C634A8E1FB29688B5CDA@MN0PR21MB3120.namprd21.prod.outlook.com>
2023-10-10 18:21 ` |SUCCESS| pw132470 [PATCH v3] " qemudev
2023-10-10 18:26 ` qemudev
2023-10-10 18:42 ` checkpatch
2023-10-10 19:59 ` 0-day Robot
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=6526208c.920a0220.4ab29.b3ccSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).