From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw127939 [PATCH] net/ice: fix outer UDP checksum offload
Date: Thu, 01 Jun 2023 19:06:51 -0700 (PDT) [thread overview]
Message-ID: <64794ebb.170a0220.930e8.0191SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/127939
_Functional Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Friday, June 02 2023 01:42:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:abaa473297cf21cb81e5348185a7694ae2f221e7
127939 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26497/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-02 2:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 2:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 22:29 dpdklab
2023-06-09 22:29 dpdklab
2023-06-09 22:20 dpdklab
2023-06-08 22:11 dpdklab
2023-06-08 22:11 dpdklab
2023-06-08 22:10 dpdklab
2023-06-08 22:09 dpdklab
2023-06-08 22:08 dpdklab
2023-06-08 22:08 dpdklab
2023-06-08 22:06 dpdklab
2023-06-02 3:50 dpdklab
2023-06-02 3:17 dpdklab
2023-06-02 3:06 dpdklab
2023-06-02 2:53 dpdklab
2023-06-02 2:34 dpdklab
2023-06-02 2:24 dpdklab
2023-06-02 2:12 dpdklab
2023-06-02 2:12 dpdklab
2023-06-02 2:08 dpdklab
2023-06-02 2:08 dpdklab
2023-06-02 2:07 dpdklab
2023-06-02 2:07 dpdklab
2023-06-02 2:07 dpdklab
[not found] <20230602014253.2347419-1-zhichaox.zeng@intel.com>
2023-06-02 1:26 ` qemudev
2023-06-02 1:30 ` qemudev
2023-06-02 1:38 ` checkpatch
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=64794ebb.170a0220.930e8.0191SMTPIN_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).