From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Alexander Kozyrev <akozyrev@nvidia.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130091 [PATCH] ethdev: add packet type matching item
Date: Thu, 10 Aug 2023 16:37:31 -0700 (PDT) [thread overview]
Message-ID: <64d574bb.810a0220.79fe.ae76SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130091
_Testing PASS_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Thursday, August 10 2023 16:14:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130091 --> testing pass
Test environment and result as below:
+-----------------+------------------------------+---------------------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest |
+=================+==============================+===========================+
| Debian 11 (arm) | PASS | PASS |
+-----------------+------------------------------+---------------------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27284/
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-10 23:37 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 23:37 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 4:00 dpdklab
2023-08-14 3:53 dpdklab
2023-08-14 3:52 dpdklab
2023-08-14 3:51 dpdklab
2023-08-14 3:50 dpdklab
2023-08-14 3:49 dpdklab
2023-08-14 3:49 dpdklab
2023-08-14 3:48 dpdklab
2023-08-14 3:47 dpdklab
2023-08-14 3:46 dpdklab
2023-08-14 3:46 dpdklab
2023-08-14 3:45 dpdklab
2023-08-14 0:22 dpdklab
2023-08-13 19:33 dpdklab
2023-08-11 20:54 dpdklab
2023-08-11 20:45 dpdklab
2023-08-11 20:40 dpdklab
2023-08-11 20:24 dpdklab
2023-08-11 20:13 dpdklab
2023-08-11 16:19 dpdklab
2023-08-11 14:51 dpdklab
2023-08-11 7:20 dpdklab
2023-08-11 2:06 dpdklab
2023-08-11 2:01 dpdklab
2023-08-11 1:50 dpdklab
2023-08-11 1:49 dpdklab
2023-08-11 1:36 dpdklab
2023-08-11 1:08 dpdklab
2023-08-11 1:05 dpdklab
2023-08-11 0:52 dpdklab
2023-08-11 0:50 dpdklab
2023-08-11 0:50 dpdklab
2023-08-11 0:41 dpdklab
2023-08-11 0:40 dpdklab
2023-08-11 0:40 dpdklab
2023-08-11 0:30 dpdklab
2023-08-11 0:28 dpdklab
2023-08-11 0:13 dpdklab
2023-08-11 0:06 dpdklab
2023-08-11 0:03 dpdklab
2023-08-11 0:01 dpdklab
2023-08-10 23:59 dpdklab
2023-08-10 23:58 dpdklab
2023-08-10 23:53 dpdklab
2023-08-10 23:52 dpdklab
2023-08-10 23:52 dpdklab
2023-08-10 23:47 dpdklab
2023-08-10 23:44 dpdklab
2023-08-10 23:44 dpdklab
2023-08-10 23:44 dpdklab
2023-08-10 23:38 dpdklab
2023-08-10 23:37 dpdklab
2023-08-10 23:37 dpdklab
2023-08-10 23:37 dpdklab
2023-08-10 23:35 dpdklab
2023-08-10 23:35 dpdklab
2023-08-10 23:33 dpdklab
2023-08-10 23:33 dpdklab
2023-08-10 23:33 dpdklab
2023-08-10 23:32 dpdklab
2023-08-10 23:31 dpdklab
2023-08-10 23:21 dpdklab
2023-08-10 22:40 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 21:22 dpdklab
2023-08-10 21:22 dpdklab
2023-08-10 21:20 dpdklab
2023-08-10 21:17 dpdklab
[not found] <20230810161447.2108369-1-akozyrev@nvidia.com>
2023-08-10 16:06 ` qemudev
2023-08-10 16:10 ` qemudev
2023-08-10 16:16 ` checkpatch
2023-08-10 17:58 ` 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=64d574bb.810a0220.79fe.ae76SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=akozyrev@nvidia.com \
--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).