From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138151 [PATCH] [V3] ethdev: restore eth_devargs init at
Date: Mon, 11 Mar 2024 07:23:06 -0700 (PDT) [thread overview]
Message-ID: <65ef13ca.170a0220.1f29d.5bc2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240311115722.2708497-1-thierry.herbelot@6wind.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138151
_Testing PASS_
Submitter: Thierry Herbelot <thierry.herbelot@6wind.com>
Date: Monday, March 11 2024 11:57:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a2a2ce171d00b8f27c8c43c37d5dd8505d8f2e89
138151 --> 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/29498/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-11 14:23 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240311115722.2708497-1-thierry.herbelot@6wind.com>
2024-03-11 11:39 ` |SUCCESS| pw138151 [V3] ethdev: restore eth_devargs init at startup of rte_eth_devargs_parse() qemudev
2024-03-11 11:44 ` qemudev
2024-03-11 11:59 ` |SUCCESS| pw138151 [V3] ethdev: restore eth_devargs init at startup of rte_eth_devargs_parse checkpatch
2024-03-11 13:02 ` |SUCCESS| pw138151 [V3] ethdev: restore eth_devargs init at startup of rte_eth_devargs_parse() 0-day Robot
2024-03-11 13:58 ` |SUCCESS| pw138151 [PATCH] [V3] ethdev: restore eth_devargs init at dpdklab
2024-03-11 13:59 ` dpdklab
2024-03-11 14:00 ` dpdklab
2024-03-11 14:01 ` dpdklab
2024-03-11 14:01 ` dpdklab
2024-03-11 14:01 ` dpdklab
2024-03-11 14:01 ` dpdklab
2024-03-11 14:01 ` dpdklab
2024-03-11 14:02 ` dpdklab
2024-03-11 14:02 ` dpdklab
2024-03-11 14:02 ` dpdklab
2024-03-11 14:02 ` dpdklab
2024-03-11 14:02 ` dpdklab
2024-03-11 14:03 ` dpdklab
2024-03-11 14:03 ` dpdklab
2024-03-11 14:03 ` dpdklab
2024-03-11 14:03 ` dpdklab
2024-03-11 14:04 ` dpdklab
2024-03-11 14:04 ` dpdklab
2024-03-11 14:04 ` dpdklab
2024-03-11 14:04 ` dpdklab
2024-03-11 14:04 ` dpdklab
2024-03-11 14:05 ` dpdklab
2024-03-11 14:05 ` dpdklab
2024-03-11 14:05 ` dpdklab
2024-03-11 14:05 ` dpdklab
2024-03-11 14:06 ` dpdklab
2024-03-11 14:06 ` dpdklab
2024-03-11 14:06 ` dpdklab
2024-03-11 14:06 ` dpdklab
2024-03-11 14:06 ` dpdklab
2024-03-11 14:07 ` dpdklab
2024-03-11 14:07 ` dpdklab
2024-03-11 14:07 ` dpdklab
2024-03-11 14:07 ` dpdklab
2024-03-11 14:07 ` dpdklab
2024-03-11 14:07 ` dpdklab
2024-03-11 14:07 ` dpdklab
2024-03-11 14:08 ` dpdklab
2024-03-11 14:08 ` dpdklab
2024-03-11 14:08 ` dpdklab
2024-03-11 14:08 ` dpdklab
2024-03-11 14:08 ` dpdklab
2024-03-11 14:08 ` dpdklab
2024-03-11 14:08 ` dpdklab
2024-03-11 14:08 ` dpdklab
2024-03-11 14:09 ` dpdklab
2024-03-11 14:09 ` dpdklab
2024-03-11 14:09 ` dpdklab
2024-03-11 14:09 ` dpdklab
2024-03-11 14:09 ` dpdklab
2024-03-11 14:10 ` dpdklab
2024-03-11 14:10 ` dpdklab
2024-03-11 14:10 ` dpdklab
2024-03-11 14:10 ` dpdklab
2024-03-11 14:10 ` dpdklab
2024-03-11 14:11 ` dpdklab
2024-03-11 14:11 ` dpdklab
2024-03-11 14:11 ` dpdklab
2024-03-11 14:11 ` dpdklab
2024-03-11 14:11 ` dpdklab
2024-03-11 14:12 ` dpdklab
2024-03-11 14:14 ` dpdklab
2024-03-11 14:14 ` dpdklab
2024-03-11 14:17 ` dpdklab
2024-03-11 14:23 ` dpdklab [this message]
2024-03-11 14:34 ` dpdklab
2024-03-11 14:59 ` dpdklab
2024-03-11 15:30 ` dpdklab
2024-03-14 22:02 ` dpdklab
2024-03-14 22:38 ` 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=65ef13ca.170a0220.1f29d.5bc2SMTPIN_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).