From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125858 [PATCH] ring: fix the variable name error
Date: Fri, 7 Apr 2023 16:27:24 +0000 (UTC) [thread overview]
Message-ID: <20230407162724.60E526012C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125858
_Testing PASS_
Submitter: Feifei Wang <feifei.wang2@arm.com>
Date: Friday, April 07 2023 08:48:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:65487b12db83c9ef37526a983c43191cd44dae99
125858 --> testing pass
Test environment and result as below:
+----------------------+---------------------------+------------------------------+--------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest |
+======================+===========================+==============================+==============+
| Debian 11 | PASS | PASS | SKIPPED |
+----------------------+---------------------------+------------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | PASS |
+----------------------+---------------------------+------------------------------+--------------+
Debian 11
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25940/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-07 16:27 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 16:27 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-07 17:20 dpdklab
2023-04-07 16:53 dpdklab
2023-04-07 16:47 dpdklab
2023-04-07 16:34 dpdklab
2023-04-07 16:23 dpdklab
2023-04-07 16:22 dpdklab
2023-04-07 16:20 dpdklab
2023-04-07 16:20 dpdklab
2023-04-07 16:15 dpdklab
2023-04-07 16:14 dpdklab
2023-04-07 16:12 dpdklab
2023-04-07 16:10 dpdklab
2023-04-07 16:09 dpdklab
2023-04-07 16:03 dpdklab
2023-04-07 16:03 dpdklab
2023-04-07 15:51 dpdklab
2023-04-07 15:46 dpdklab
2023-04-07 15:24 dpdklab
2023-04-07 15:19 dpdklab
2023-04-07 15:18 dpdklab
2023-04-07 15:18 dpdklab
2023-04-07 15:18 dpdklab
2023-04-07 15:16 dpdklab
2023-04-07 15:15 dpdklab
2023-04-07 15:15 dpdklab
2023-04-07 15:14 dpdklab
2023-04-07 15:13 dpdklab
2023-04-07 15:11 dpdklab
2023-04-07 15:07 dpdklab
2023-04-07 15:06 dpdklab
2023-04-07 15:04 dpdklab
2023-04-07 15:01 dpdklab
2023-04-07 15:00 dpdklab
2023-04-07 14:57 dpdklab
2023-04-07 14:55 dpdklab
2023-04-07 14:55 dpdklab
2023-04-07 14:55 dpdklab
2023-04-07 14:52 dpdklab
2023-04-07 14:51 dpdklab
2023-04-07 14:50 dpdklab
2023-04-07 14:48 dpdklab
2023-04-07 14:48 dpdklab
2023-04-07 14:46 dpdklab
2023-04-07 14:46 dpdklab
2023-04-07 14:42 dpdklab
2023-04-07 14:41 dpdklab
2023-04-07 14:39 dpdklab
2023-04-07 14:34 dpdklab
2023-04-07 14:31 dpdklab
[not found] <20230407084826.2159688-1-feifei.wang2@arm.com>
2023-04-07 8:37 ` qemudev
2023-04-07 8:41 ` qemudev
2023-04-07 8:49 ` checkpatch
2023-04-07 9: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=20230407162724.60E526012C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).