From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| pw159606 [PATCH] crypto/openssl: Add support for SHA3 algo
Date: Wed, 07 Jan 2026 18:30:09 -0800 (PST) [thread overview]
Message-ID: <695f16b1.050a0220.3436c5.393cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20260106130926.2267677-1-emma.finn@intel.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/159606
_Testing PASS_
Submitter: Emma Finn <emma.finn@intel.com>
Date: Tuesday, January 06 2026 13:09:26
DPDK git baseline: Repo:dpdk-next-crypto
Branch: master
CommitID:cd60dcd503b91956f966a1f6d595b35d256ac00f
159606 --> testing pass
Upstream job id: Generic-DPDK-Compile-Meson#454260
Test environment and result as below:
+-----------------+--------------------+
| Environment | dpdk_meson_compile |
+=================+====================+
| Fedora Linux 42 | PASS |
+-----------------+--------------------+
| Ubuntu 20.04 | PASS |
+-----------------+--------------------+
Fedora Linux 42
Kernel: 5.4
Compiler: gcc gcc (GCC) 15.2.1 20251111 (Red Hat 15.2.1-4)
Ubuntu 20.04
Kernel: 5.4
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/34799/
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:[~2026-01-08 2:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260106130926.2267677-1-emma.finn@intel.com>
2026-01-06 13:10 ` |SUCCESS| pw159606 [PATCH] crypto/openssl: Add support for SHA3 algorithms checkpatch
2026-01-06 14:01 ` qemudev
2026-01-06 14:06 ` qemudev
2026-01-06 14:07 ` 0-day Robot
2026-01-06 14:07 ` 0-day Robot
2026-01-07 18:06 ` |SUCCESS| pw159606 [PATCH] crypto/openssl: Add support for SHA3 algo dpdklab
2026-01-07 18:07 ` dpdklab
2026-01-07 21:17 ` dpdklab
2026-01-07 21:47 ` dpdklab
2026-01-07 23:10 ` dpdklab
2026-01-08 1:50 ` |PENDING| " dpdklab
2026-01-08 2:03 ` dpdklab
2026-01-08 2:04 ` |SUCCESS| " dpdklab
2026-01-08 2:30 ` dpdklab [this message]
2026-01-08 9:17 ` dpdklab
2026-01-08 12:08 ` dpdklab
2026-01-08 20:21 ` dpdklab
2026-01-08 21:25 ` dpdklab
2026-01-08 21:25 ` dpdklab
2026-01-08 21:49 ` dpdklab
2026-01-08 23:20 ` dpdklab
2026-01-08 23:49 ` dpdklab
2026-01-08 23:58 ` 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=695f16b1.050a0220.3436c5.393cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=gakhil@marvell.com \
--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).