From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129915 [PATCH] net/mlx5: fix bond resource release
Date: Sat, 05 Aug 2023 03:34:18 -0700 (PDT) [thread overview]
Message-ID: <64ce25aa.810a0220.5d669.15ebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129915
_Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Friday, August 04 2023 17:15:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9836014d4c2b1b2c29948c928fd386b2944b6bcf
129915 --> 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/27235/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-05 10:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 10:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-05 11:45 dpdklab
2023-08-05 11:28 dpdklab
2023-08-05 11:24 dpdklab
2023-08-05 11:24 dpdklab
2023-08-05 11:19 dpdklab
2023-08-05 11:06 dpdklab
2023-08-05 11:02 dpdklab
2023-08-05 10:49 dpdklab
2023-08-05 10:34 dpdklab
2023-08-05 10:26 dpdklab
2023-08-05 10:10 dpdklab
2023-08-05 10:02 dpdklab
2023-08-05 9:59 dpdklab
2023-08-05 9:51 dpdklab
2023-08-05 9:50 dpdklab
2023-08-05 9:45 dpdklab
2023-08-05 9:45 dpdklab
2023-08-05 9:41 dpdklab
2023-08-05 9:40 dpdklab
[not found] <20230804171536.1724554-1-dsosnowski@nvidia.com>
2023-08-04 17:03 ` qemudev
2023-08-04 17:07 ` qemudev
2023-08-04 17:17 ` checkpatch
2023-08-04 18:38 ` 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=64ce25aa.810a0220.5d669.15ebSMTPIN_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).