From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139165 [PATCH] MAINTAINERS: remove maintainers that boun
Date: Fri, 05 Apr 2024 15:39:45 -0700 (PDT) [thread overview]
Message-ID: <66107db1.050a0220.4bf2d.8a09SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240405170514.369037-1-stephen@networkplumber.org>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139165
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, April 05 2024 17:05:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139165 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29727/
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-04-05 22:39 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240405170514.369037-1-stephen@networkplumber.org>
2024-04-05 16:46 ` |SUCCESS| pw139165 [PATCH] MAINTAINERS: remove maintainers that bounce qemudev
2024-04-05 16:50 ` qemudev
2024-04-05 17:05 ` checkpatch
2024-04-05 21:04 ` 0-day Robot
2024-04-05 21:44 ` |SUCCESS| pw139165 [PATCH] MAINTAINERS: remove maintainers that boun dpdklab
2024-04-05 21:45 ` dpdklab
2024-04-05 21:46 ` dpdklab
2024-04-05 21:46 ` dpdklab
2024-04-05 21:46 ` dpdklab
2024-04-05 21:48 ` dpdklab
2024-04-05 22:10 ` dpdklab
2024-04-05 22:11 ` dpdklab
2024-04-05 22:11 ` dpdklab
2024-04-05 22:11 ` dpdklab
2024-04-05 22:11 ` dpdklab
2024-04-05 22:11 ` dpdklab
2024-04-05 22:11 ` dpdklab
2024-04-05 22:12 ` dpdklab
2024-04-05 22:12 ` dpdklab
2024-04-05 22:12 ` dpdklab
2024-04-05 22:12 ` dpdklab
2024-04-05 22:13 ` dpdklab
2024-04-05 22:13 ` dpdklab
2024-04-05 22:13 ` dpdklab
2024-04-05 22:13 ` dpdklab
2024-04-05 22:13 ` dpdklab
2024-04-05 22:14 ` dpdklab
2024-04-05 22:14 ` dpdklab
2024-04-05 22:15 ` dpdklab
2024-04-05 22:15 ` dpdklab
2024-04-05 22:15 ` dpdklab
2024-04-05 22:15 ` dpdklab
2024-04-05 22:15 ` dpdklab
2024-04-05 22:16 ` dpdklab
2024-04-05 22:16 ` dpdklab
2024-04-05 22:17 ` dpdklab
2024-04-05 22:17 ` dpdklab
2024-04-05 22:17 ` dpdklab
2024-04-05 22:17 ` dpdklab
2024-04-05 22:17 ` dpdklab
2024-04-05 22:17 ` dpdklab
2024-04-05 22:18 ` dpdklab
2024-04-05 22:18 ` dpdklab
2024-04-05 22:18 ` dpdklab
2024-04-05 22:18 ` dpdklab
2024-04-05 22:18 ` dpdklab
2024-04-05 22:18 ` dpdklab
2024-04-05 22:18 ` dpdklab
2024-04-05 22:18 ` dpdklab
2024-04-05 22:18 ` dpdklab
2024-04-05 22:18 ` dpdklab
2024-04-05 22:19 ` dpdklab
2024-04-05 22:19 ` dpdklab
2024-04-05 22:19 ` dpdklab
2024-04-05 22:19 ` dpdklab
2024-04-05 22:19 ` dpdklab
2024-04-05 22:19 ` dpdklab
2024-04-05 22:20 ` dpdklab
2024-04-05 22:20 ` dpdklab
2024-04-05 22:20 ` dpdklab
2024-04-05 22:20 ` dpdklab
2024-04-05 22:20 ` dpdklab
2024-04-05 22:21 ` dpdklab
2024-04-05 22:21 ` dpdklab
2024-04-05 22:21 ` dpdklab
2024-04-05 22:21 ` dpdklab
2024-04-05 22:21 ` dpdklab
2024-04-05 22:22 ` dpdklab
2024-04-05 22:23 ` dpdklab
2024-04-05 22:24 ` dpdklab
2024-04-05 22:24 ` dpdklab
2024-04-05 22:25 ` dpdklab
2024-04-05 22:26 ` dpdklab
2024-04-05 22:27 ` dpdklab
2024-04-05 22:28 ` dpdklab
2024-04-05 22:28 ` dpdklab
2024-04-05 22:30 ` dpdklab
2024-04-05 22:37 ` dpdklab
2024-04-05 22:39 ` dpdklab [this message]
2024-04-05 22:48 ` dpdklab
2024-04-05 23:10 ` dpdklab
2024-04-05 23:11 ` dpdklab
2024-04-05 23:12 ` dpdklab
2024-04-05 23:16 ` dpdklab
2024-04-05 23:19 ` dpdklab
2024-04-05 23:23 ` dpdklab
2024-04-05 23:24 ` dpdklab
2024-04-06 3:00 ` dpdklab
2024-04-06 3:36 ` 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=66107db1.050a0220.4bf2d.8a09SMTPIN_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).