From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155203 [PATCH] net/ice: fix VLAN tag reporting on Rx
Date: Mon, 14 Jul 2025 14:23:40 -0700 (PDT) [thread overview]
Message-ID: <6875755c.050a0220.89074.b19fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250714161050.289375-1-bruce.richardson@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/155203
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, July 14 2025 16:10:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a6b10031d251fcc7dadede461f7e1d005024b139
155203 --> testing pass
Upstream job id: ACVP-FIPS-testing#10500
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33650/
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:[~2025-07-14 21:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250714161050.289375-1-bruce.richardson@intel.com>
2025-07-14 15:37 ` qemudev
2025-07-14 15:41 ` qemudev
2025-07-14 16:10 ` checkpatch
2025-07-14 16:49 ` dpdklab
2025-07-14 16:57 ` dpdklab
2025-07-14 17:02 ` |PENDING| " dpdklab
2025-07-14 17:03 ` dpdklab
2025-07-14 17:11 ` dpdklab
2025-07-14 17:19 ` dpdklab
2025-07-14 17:24 ` |SUCCESS| " 0-day Robot
2025-07-14 17:29 ` |PENDING| " dpdklab
2025-07-14 17:31 ` |SUCCESS| " dpdklab
2025-07-14 18:08 ` dpdklab
2025-07-14 18:27 ` dpdklab
2025-07-14 19:51 ` dpdklab
2025-07-14 20:43 ` dpdklab
2025-07-14 21:23 ` dpdklab [this message]
2025-07-14 21:59 ` 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=6875755c.050a0220.89074.b19fSMTPIN_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).