From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135131 [PATCH] [v4] lib/net: fix tcp/udp cksum with padd
Date: Wed, 13 Dec 2023 10:50:44 -0800 (PST) [thread overview]
Message-ID: <6579fd04.050a0220.47094.3929SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135131
_Testing PASS_
Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Wednesday, December 13 2023 04:37:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
135131 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28606/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-13 18:50 UTC|newest]
Thread overview: 108+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 18:50 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-13 20:00 dpdklab
2023-12-13 19:59 dpdklab
2023-12-13 19:53 dpdklab
2023-12-13 19:13 dpdklab
2023-12-13 17:52 dpdklab
2023-12-13 17:51 dpdklab
2023-12-13 17:32 dpdklab
2023-12-13 17:32 dpdklab
2023-12-13 17:29 dpdklab
2023-12-13 17:29 dpdklab
2023-12-13 17:29 dpdklab
2023-12-13 17:26 dpdklab
2023-12-13 17:25 dpdklab
2023-12-13 17:23 dpdklab
2023-12-13 17:23 dpdklab
2023-12-13 17:23 dpdklab
2023-12-13 17:21 dpdklab
2023-12-13 17:19 dpdklab
2023-12-13 17:19 dpdklab
2023-12-13 17:19 dpdklab
2023-12-13 17:18 dpdklab
2023-12-13 17:18 dpdklab
2023-12-13 17:17 dpdklab
2023-12-13 17:17 dpdklab
2023-12-13 17:17 dpdklab
2023-12-13 17:17 dpdklab
2023-12-13 17:16 dpdklab
2023-12-13 17:16 dpdklab
2023-12-13 17:16 dpdklab
2023-12-13 17:00 dpdklab
2023-12-13 16:58 dpdklab
2023-12-13 16:57 dpdklab
2023-12-13 16:57 dpdklab
2023-12-13 16:56 dpdklab
2023-12-13 16:53 dpdklab
2023-12-13 16:33 dpdklab
2023-12-13 16:14 dpdklab
2023-12-13 15:59 dpdklab
2023-12-13 15:49 dpdklab
2023-12-13 15:48 dpdklab
2023-12-13 15:33 dpdklab
2023-12-13 15:33 dpdklab
2023-12-13 11:05 dpdklab
2023-12-13 10:45 dpdklab
2023-12-13 10:43 dpdklab
2023-12-13 10:37 dpdklab
2023-12-13 10:32 dpdklab
2023-12-13 10:30 dpdklab
2023-12-13 10:28 dpdklab
2023-12-13 10:27 dpdklab
2023-12-13 10:27 dpdklab
2023-12-13 10:26 dpdklab
2023-12-13 10:24 dpdklab
2023-12-13 10:23 dpdklab
2023-12-13 10:19 dpdklab
2023-12-13 10:19 dpdklab
2023-12-13 10:17 dpdklab
2023-12-13 10:15 dpdklab
2023-12-13 10:15 dpdklab
2023-12-13 10:13 dpdklab
2023-12-13 10:12 dpdklab
2023-12-13 10:10 dpdklab
2023-12-13 10:10 dpdklab
2023-12-13 10:08 dpdklab
2023-12-13 10:07 dpdklab
2023-12-13 10:05 dpdklab
2023-12-13 10:05 dpdklab
2023-12-13 10:02 dpdklab
2023-12-13 9:51 dpdklab
2023-12-13 9:48 dpdklab
2023-12-13 9:03 dpdklab
2023-12-13 9:02 dpdklab
2023-12-13 8:49 dpdklab
2023-12-13 8:48 dpdklab
2023-12-13 8:44 dpdklab
2023-12-13 8:41 dpdklab
2023-12-13 8:39 dpdklab
2023-12-13 8:38 dpdklab
2023-12-13 8:37 dpdklab
2023-12-13 8:30 dpdklab
2023-12-13 8:24 dpdklab
2023-12-13 8:23 dpdklab
2023-12-13 8:15 dpdklab
2023-12-13 8:14 dpdklab
2023-12-13 8:11 dpdklab
2023-12-13 8:07 dpdklab
2023-12-13 7:52 dpdklab
2023-12-13 7:51 dpdklab
2023-12-13 7:51 dpdklab
2023-12-13 7:46 dpdklab
2023-12-13 7:45 dpdklab
2023-12-13 7:34 dpdklab
2023-12-13 7:18 dpdklab
2023-12-13 7:18 dpdklab
2023-12-13 7:16 dpdklab
2023-12-13 7:14 dpdklab
2023-12-13 7:14 dpdklab
2023-12-13 7:14 dpdklab
2023-12-13 7:13 dpdklab
2023-12-13 7:12 dpdklab
2023-12-13 7:12 dpdklab
2023-12-13 7:12 dpdklab
2023-12-13 7:12 dpdklab
2023-12-13 7:11 dpdklab
2023-12-13 6:51 dpdklab
2023-12-13 6:48 dpdklab
2023-12-13 6: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=6579fd04.050a0220.47094.3929SMTPIN_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).